Service design: anticipating how a place or a service will be used before it's built
How do you know what people will do in a place or a service that doesn't exist yet?
It's the question we get asked most. We meet the future users, look at comparable situations, model behaviour profiles and project them onto the plans: which journeys take shape, from point A to point B, and how those flows become services. It's the same craft as our UX design, except there's not necessarily a digital interface at the end.
When we get called in
The projects we're given most often start from one of these situations.
- A place is about to open or be refurbished, and you want to know how it will be used before committing to the works.
- Several audiences will share the same spot, and the spaces and flows have to be sized so that everyone finds their place.
- Your service already runs, and you want to see how it performs on the ground. That's the case of the Paléo Festival, where we observe the experience of 250,000 festival-goers and 5,000 volunteers.
- Your service is spread across several places, several operators and several steps. With SNCF Voyageurs TER Nouvelle-Aquitaine, we worked on the last miles between train stations and four tourist destinations.
- An offer has to be built with players who hadn't worked together yet, like the tourism players of a region brought together around one project.
The users, and the people who keep the service running
A user is a customer, a visitor, a traveller. It's also the people who operate the service day to day and those who steer it. We don't do user-centred design, we do stakeholder-centred design: we take the uses on both sides and look for the solution that makes the best compromise, rather than imagining a solution on one side and measuring its impact on the other afterwards.
Our service design approach
We go and meet the future users
Interviews with the people who will use the place, on site when possible, and visits to comparable situations elsewhere, to see what's already at play there.
We model behaviour profiles
The research produces personas, which segment behaviours, and journeys that project them onto the sequence of actions. That's what we rely on afterwards to reason about the place.
We project the journeys onto the plans
We look at how people get from one point to another in the place, as a pedestrian would, which flows take shape, and how those flows become services.
Co-built when the framework allows it
Working with your stakeholders is more useful on every project, but it takes time and means getting them together. When the schedule or the budget don't allow it, we work on our side and discuss the results with you afterwards.
We prioritise with the Kano model
For each functional scope, we look at how the presence or absence of a service affects users' satisfaction. That's what gives a reasoned prioritisation of uses.
You make the call
We qualify the effect on users, and you set that prioritisation against your constraints and your budget. The decision is yours, and we can support you in the trade-offs.
What you get with service design
Personas, an experience map and a service blueprint
The personas segment the behaviours of the different types of users. The experience map projects those behaviours onto the sequence of actions in the journey. The service blueprint adds what happens backstage: it links the user's journey to the actions of the people running the place, staff included, so you see all the players together. This modelling is what holds the reasoning together, and what we come back to when we justify the recommendations.
Journeys projected onto the place
The routes, the decision points and the flows between spaces or between steps of the service, as they take shape from the uses we've recorded.
A prioritised functional list
What's expected, scope by scope, ranked by its effect on users' satisfaction. It's the deliverable you use to decide, more than the models that produced it.
An analysis report and recommendations
Reasoned recommendations, backed by the study we ran and as complete as possible. They inform the decision, they don't make it for you.
250,000 festival-goers, and what the field reveals
At the Paléo Festival, in the 2018 edition, the signage got 80% satisfaction. Out on the ground, though, we watch a festival-goer who has to turn back because the campsite is outside, parents bounced from one desk to the next for noise-cancelling headphones, a festival-goer who leaves the festival because they can't find the information stand. These breaks are invisible from inside the organisation. The diagnosis laid out seventeen areas of recommendation and three principles: dialogue between sectors, continuous information on the ground, observation of real uses. The following year, a mobile information team was being tested and the plans reworked, and we went back to observe what those choices did in practice.
Read the case studyService design for an insurer, regions linked to their train stations, a tourist office
Once off the TER train, how do you get to where you are staying?
And after the train, how do we get home?
When a future Tourist Office is built through workshops
From a shared reference to the OTI action planFrequently asked questions
Designing a service starting from how it's used: understanding what the different people who will use it and keep it running need, then turning that knowledge into journeys, a functional scope and recommendations. With us, it most often concerns a physical place rather than an interface.
It's the same craft, applied to something other than an interface. When people talk about experience design, they usually mean digital experience. Here, service design is an output of the user research: as soon as we have the findings, we start thinking about uses, journeys and functional scope, whether or not there's a screen at the end.
Interviews with future users or observation of the existing service, visits to comparable situations, modelling of profiles, projection of journeys onto the plans, prioritisation by effect on satisfaction, then a debrief. Depending on budget and schedule, all or part of it is done in workshops with your stakeholders.
No, not necessarily. There can be one, and we've also worked on a mobile app, but it's a small piece. When there isn't one, it doesn't change the approach.
Yes. Putting ourselves at the service of the community and building tools that serve citizens is part of our very purpose. We bring in the reality of the field, on the user side as well as the staff side.