I love Service Design but…
This is not a rant I promise – it’s more of a confession and acknowledgment that, as in any work, there are good and bad sides to it. More often we aren’t as willing to share the bad difficult parts (which is ok, too), however if you are willing to share it can be good to do so. Sharing helps us build conversations around things that we struggle with and enables us to help each other in ways to combat the difficult parts. Therefore this is not a rant (I’m 70% sure of that) rather a sharing post in which I will be talking about my current buts (pun intended) of service design:
I LOVE SERVICE DESIGN BUT…
Working with stakeholders* who aren’t aware of what I do can be mentally exhausting.
(*Stakeholders are people in your client’s organisation that share a stake, responsibility, or ownership in your project.)
Working with stakeholders is a crucial part of our work, they present and understand the business aspect that needs to be considered in the creation or maintenance of the services we are working on. They are the people who will be responsible for the service as well as delivery of that service after we are gone (speaking from the perspective of a consultant designer). However, the majority of the time working with stakeholders is hard, they have their own pressures, things to deliver, opinions to share and people to please, as well as more often than not lack of understanding in what we do, and why our work is important.
When we’re brought in to do work with a client, the people who are the least responsive or care the least are usually the people who were not part of the decision making process of getting us in. That usually means we spend time validating why we’re there and it takes a while to build trust. With the increasing pressure of time we have on a project and the feeling of running in circles with conversations about what design or services are, and why users are important to listen to, it can be mentally exhausting.
So how to break the cycle? Or make it a bit easier? Change the but…
- I can feel a shift in organisations’ understanding, which is also part of their responsibility to educate, inform and support their employees with the understanding that is needed to work with us. Although the majority of the work is still on us, more and more organisations are building internal teams and support to help their employees understand better the work we are doing.
- For example, some of the government departments we work with offer classes and workshops so that people can get better knowledge of what our work achieves and even decide to immerse themselves in design with the help of specialists to practise design and user research themselves.
- We are gaining experiences and sharing knowledge. Interaction with stakeholders is different on every project we work on and so we build a better understanding of what works and what doesn’t work. So we are better prepared for the interactions.
- Having a service design community of practice gives us dedicated time in which we can share our knowledge and support each other.
- Asking for support. It is important to know when you have reached your limits and how you can reach out. We aren’t superheroes, we’re only human (most of the time) therefore there is nothing wrong in recognising that we need support. People should be encouraged to seek out support when they need it.
I LOVE SERVICE DESIGN BUT…
Making people understand that I’m not there to fight them but help them is a fight on its own.
As consultants, we are usually the people from the outside coming into organisations, asking to speak to people, taking their time from their day-to-day work (which is usually already full by default). Most times we aren’t introduced to those people, who we would otherwise work well with, therefore the first experience of who we are and what we are here to do isn’t great. It’s natural for people to feel protective of their work, we all do. When your job is to look at processes and ways of working, quite often that is met with an assumption that you are there to tell people what they’ve been doing wrong. It can quickly get defensive and people shut down which makes it harder for us to work with them and do our jobs. At the end of the day I have the skills but they have the knowledge and I can’t do my job without them.
So how to break the cycle? Or make it a bit easier? Change the but…
- I try to get to know people that I work with, learn about their understanding of my work and incorporate teaching of what I do in our future work if I see it would be helpful.
- Something I haven’t used before to help this “but” is the user-centric maturity model that helps us see where our clients’ understanding of our work is and can help inform how we approach and work with them. This twitter thread might give you some of the resources if people similar to me are new to this.
- In every project I want to meet people, so I book in one-to-one chats with them so that we can get to know each other. That also gives me an opportunity to make them feel more comfortable working with me.
- I make it very clear that I’m not here to judge their work and processes but to see how we can work together to make them better. Most people are working in broken systems and need to carve out a workspace that is workable for them. Only as a team can we make the difference and improve the processes that need to be carved out.
- In any workshop I facilitate I have a code of conduct that states all of the above. And if necessary I repeat it verbally as well.
I LOVE SERVICE DESIGN BUT…
On many occasions the core of the problems that we try to solve lie outside our scope and that feels like our solutions will make the problem better, but not solve it as would be our intention.
The majority of projects that we uptake are centred around the bottom line (services that are client facing but under systems, constraints and guidance that is decided, much higher up in the organisation). That usually means that the services we work on are trying to solve core problems that are happening on levels we aren’t able to access.
So how to break the cycle? Or make it a bit easier? Change the but…
- Connecting with people who can make a difference. I try to find who in the organisation can make the difference or would be responsible for what we need to solve. They might be already aware of the problem and I can help them build the evidence that they need for change. In doing so we can also showcase the need for service design to be considered and present at higher levels in the organisation.
- Working in the open and sharing my work across an organisation invites collaboration and expands the impact of the work.
- On the Secure DfE data project, we’d identified that Information Security Officers (ISOs) and people in the Project Management Office (PMO) were very disconnected and that was causing pain to users. Any suggestions of working with them were shut down as this was not in scope. Eventually, PMO people came to our show and tell and told us they’ve been doing similar work and that they wanted to work together.
- If I’m working on a service that is connected with other services, if possible I try to work and share where applicable with them. There is a true power in communities working together in the same system.
- On a recruitment, joiners, movers, leavers (RJML) system project we were looking at a system that is supported by 10 teams. We found the points in which they can work together to solve a problem as a collective.
- Handover notes or recommendations are always a good way to make sure that knowledge is kept but also shared with people who might be able to make a difference.
- As always and personally the hardest thing to accept is to recognise you can’t change the whole system overnight. Small steps in the right direction and setting up an iterative way forward is enough sometimes. Remember Rome wasn’t built in a day!
I LOVE SERVICE DESIGN BUT…
It can be hard to find a balance between stakeholder management and design work.
Speaking to people is a very important part of our work, however it can take over our time which means our design work might suffer because of it. Sometimes it feels like I have to hide away just so that I do have time and space to do service design.
So how to break the cycle? Or make it a bit easier? Change the but…
- Book time in the calendar that is dedicated to design work.
- I speak to my team, see if people can support and help me with work, who can speak to who, what relationship management needs to have me involved and what can be picked up by, for example a delivery manager.
- On multiple projects I created a list of questions that I asked my team about to see if they can be answered so that I don’t have to go to stakeholders. I have asked user researchers if they can learn more about certain topics that were still blind spots in their research sessions, and spoken to business analysts to uncover data questions, policies and governance. I’ve been through my work with a subject matter expert to clarify my understanding and started to map the processes in the time I had with stakeholders, which works well for them to observe and learn about my processes and work.
I LOVE SERVICE DESIGN BUT…
Balancing user needs, business requirements, services and processes as well as people’s capabilities is a hard task.
As service designers we are the people who are making sure that user needs are leading our design decisions and informing our work. However in reality that can be a struggle. Budget, capabilities and organisational structures and policies can constrain what an organisation is able to provide and do to meet user needs.
So how to break the cycle? Or make it a bit easier? Change the but…
- Working in the open and bringing stakeholders along on the journey, sharing often, making sure that people are aware of user needs and how they fit with the needs of the business, and how we can balance them and accommodate them.
- On the Secure DfE Data project we had to go with a platform option that wasn’t the most ideal for users but it was a platform that was already used in the organisation, so it wouldn’t cost the organisation, and we could make changes to the platform in house. We built a prototype that wasn’t tied to a particular platform and focused on content that meets user needs, then introduced the content and user needs to the in-house platform team to see how we can meet the needs and content requirements through the platform..
- Good communication about what is possible with the time and team you have. If I have 8 weeks and x members of the team, asking what we can do in that time and why we are focusing on those particular things.
- On Secure DfE Data, we had 8 weeks to conduct an Alpha with 12 hypotheses. We had to prioritise and scope down to what we could deliver in 8 weeks that would bring us the most value. We decided on particular user groups and justified them, and selected the 3 most important hypotheses that we wanted to test in the 8 weeks that we had.
- When creating recommendations, offer a range of them. For example if there are budgetary issues, prioritise based on cost vs problem or business vs user needs, and capture risks as well as communicate them to decision makers to ensure they are aware and responsible for their decision.
- Include the most user centred recommendations in future iterations or considerations for improvement.
These are my current buts in service design. Just writing them out felt good (maybe it was a bit of a rant… or rather let me call it a reflection). It does feel good to share them with others and I hope this will help people share theirs or see they aren’t the only ones maybe struggling with similar or the same buts. I know there’s always going to be ‘buts’ – it’s a tough job that we do (that’s part of what makes it exciting) but (and this is the biggest one) a very rewarding job…
Follow Paper on LinkedIn