Designing whole services

A follow-up to a space for service design.

The first Government project I worked on was a licensing service. As part of the project, the license numbers were updated. That change stopped users from being able to log into a different but related service.

In summary, our service had broken someone else’s service.

I’ve seen loads of examples of similar issues over the last 5 years. Usually the result of designing parts of services or single interactions in isolation.

So how can we start to design whole services as a user would define them?

The logical place to start would be to hire some service designers. I’m a little wary of this though, service designers aren’t a magical quick fix.

For example, adding service designers to the product teams we already have won’t help us change the things we design. Instead, we will create a lot of overlap with existing UCD roles working in the same spaces.

There are other things to resolve too like:

What is a service? Can we define it consistently across the department?

What do service designers Do? We need to define what service designers do in a way none designers understand and a way that highlights the difference between service design and interaction design.

What projects do service designers work on? We need to create the right spaces or teams for service designers to work in.

How can we increase our service design capabilities? Hiring service designers is hard especially with the money on offer outside of Government. We need a way for existing Civil Servants to move into the role.

What is a service?

Starting with what is a service. We need to be much clearer on what we class as a service and what is a part of a service. In the example, I mentioned at the start both things were called services, but none of them should be.

A service should be something that helps someone to do something or achieve a goal. A service is not a form, a portal, a microsite, or a permit. These are smaller things people need to do to complete a larger task.

For Defra, it’s things like managing my farm and going fishing.

These services include smaller interactions that build-up to one goal like buying a fishing license, submitting catch returns, and having a license checked at the river bank.

I know a lot of this has been discussed many times in the past but we still have a habit of calling everything a service. And that is one of the biggest blockers to changing how we work.

So inspired by Paul’s work at DVSA we’ve been trying to define the different things we deliver.

So far we have:

• A component - which is a single thing that could be used on multiple products and services
• A Product - which is a single interaction by a user with the organisation, usually one step in a larger user journey
• A Service - A service has multiple touch-points or interactions and that’s where a service designer should be.

We also have a collection of services together that makeup ‘a whole service’ or programme of work.

Whole Services like this transcend delivery or product teams and even organisations. This is where we could use a principal service designer.

We've also got a collection of products that don't make up one whole service, like our permitting programme. A collection of products would still benefit from consistency in design and approach but that’s probably more interaction design then service design.

What do service designers do?

Now we can define the projects service designers work on we need to clearly describe what service designers do to people who don’t have a background in design.

I think some of the biggest misconceptions about service designers are that:

• They work in the Discovery phase
• They design the ‘end-to-end journey’ of a single transaction or interaction
• They are responsible for mapping out existing services
• They do the offline or ‘none website’ things

Definitions like this don’t help to differentiate the role from other UCD disciplines which makes it hard to explain and therefore sell the value service designers bring.

So I tried to find a way of defining what service designers do based on the spaces they work in not tasks they might do.

One of the best definitions I found is this one…

I think this relates to a lot of government services that are already in existence and formed organically around the organisation's structure, data sets, or funding silos.

Another definition I like is problem framing, leaving the problem-solving part to Interaction design:

This relates to the upfront work needed to shape future projects making sure we solve the right problems.

The definition we are using now builds on these two quotes.

This definition helps us to focus more on the spaces and teams that service designers operate in instead of the skills they might have.

Project scoping

When a project reaches Discovery a lot of key decisions have already been made.

Service design has generally been bought in at Discovery or even Alpha stages so we are playing catch up which can be considered disruptive if we start to challenge some of those decisions.

The Project scoping phase is about making sure we solve the right problems and focus any resulting Discoveries on outcomes, not solutions or technology.

Programme teams

The second part of the description and the biggest part is programme teams. Services as end-users would understand them are bigger than any 1 delivery or product team. So a service designer should work across multiple delivery teams.

This will help us to:

• Solve problems that sit outside the normal remit of interaction designers on delivery teams
• Build context and understanding of end-users lives
• Highlight organisational and structural issues that prevent good service design

Where do services designers work?

The definition starts to answer this question for us, but the projects also need to be right.

A service designer on their own won't change anything. We need stakeholder buy-in and a whole team approach for things to really work.

Scoping projects

Last year we got the perfect brief to get a service designer involved in some upfront work.

We want to find out how we can deal with outbreaks of disease in trees and plants more effectively and more efficiently.

They joined a pre-discovery team for 3 months, these projects traditionally have a Project Manager a BA, and an Architect.

The first thing we learned was that there are a lot more steps before the before stage. People had been working on the project for months and already had ideas about the solution and the technology.

It was an intense 3 months trying to push back on that approach whilst also trying to understand how the organisation worked and where the opportunities were.

The resulting programme of work did end up with probably the best service design brief I’ve had. I was asked for a service designer to help them improve outcomes through the re-design of the user-facing service, business processes, and better collaboration across systems.

I hope this brief was the result of the pre-work done.

We want to do much more of this type of work but there are a couple of challenges including:

• Recruitment - It’s always hard to get someone in for short 3 month contracts
• Knowledge transfer - There’s a natural gap between this phase one any discovery work meaning we lose the Service designer and the knowledge and trust they built up

Long term we could address these issues with a permanent shaping or scoping service design role. We should be able to make that happen if we can prove this type of work is a recurring thing.

Programme teams

We have also been positioning service designers outside of project teams into the programme space. We started with a trial and the aim of proving that having someone work across teams would help us to deliver more joined-up services and work on areas deemed out of scope for the current project teams.

Some of the challenges we faced with this work include:

• Funding- We didn't charge for the first 6 months but after that, we had to work out how a role that sits across teams is funded
• Service ownership - Organisations are not always structured around user-facing services, so finding someone responsible for the whole service is tricky
• Uncertainty - The role needs someone who is comfortable with a lot of uncertainty, by working across teams there can be a lack of structure and guidance

We got some really positive feedback from the programme who said the last 12 months had helped them identify:

• Individual service improvement requirements
• Gaps in their combined service offering
• And collective developments that they need to implement across their estate

The next step for this piece of work is to support the organisation to hire their own permanent service designer and have them embedded into their leadership team without losing the connections to the service design community.

Off the back of that work, we are hiring 2 permanent principal service designers to work across our Farming and Trade portfolios.

How do we increase our Service design capability?

Hiring Service designers is probably the most difficult part of my job. At the moment we have:

• Practitioner roles at G6 to look across the whole service
• Senior roles at G7 working on services

We rely on contractors to fill gaps whilst we try to grow the permanent team. This is something we might always need to do to help upskill existing team members.

We want to create a structure where designers can move from interaction to service and are thinking of starting out with more generic design roles at junior level so people can experience both disciplines.

We are also looking at creating a pathway for people to move sideways into service design from other roles like content design.

Share on Bluesky

Share on Twitter