Choosing a Mapping Approach

Three mapping approaches cover most service design challenges. 

A service journey map visualises the steps a specific user takes to reach a specific goal, tracking their actions, thoughts and emotions over time (Gibbons, 2018). 

A service blueprint takes that same journey and adds what the organisation does to deliver it: frontstage actions visible to the user, backstage actions that support them, and the processes and evidence that connect the two (Gibbons, 2017). 

An ecosystem map takes a wider view again, showing the range of actors, channels and touchpoints that make up a service, without following one user’s step-by-step path (Grimes, 2019).

Kalbach (2020) suggests the choice comes down to three questions: what relationship within the service is being examined, whose viewpoint the map should take, and what need the map is meant to serve. A journey map fits when the need is to understand and prioritise a user’s experience, building empathy and surfacing pain points from their point of view (Gibbons and Kendrick, 2019). A blueprint fits when the need is to fix the operational causes behind those pain points, coordinating people, technology and process across departments; it suits services that are omnichannel, involve several touchpoints, or need cross-functional agreement (Gibbons and Kendrick, 2019). An ecosystem map fits earliest in a project, when the need is simply to grasp how complex a service already is and build shared understanding among stakeholders, before detailed journey mapping or blueprinting begins (Grimes, 2019).

The evidence each map depends on, also differs. A journey map needs research that captures a real user’s thoughts and feelings rather than assumptions: interviews, field studies and diary studies, checked where possible against existing data such as support logs or analytics (Kaplan, 2019). A blueprint depends more on internal evidence: employee interviews, workshops and existing operational data, gathered from the departments that own each part of the process, alongside the customer actions already established through journey mapping (Gibbons and Kendrick, 2019). An ecosystem map relies less on fresh primary research and more on knowledge already held by the team; it is best built collaboratively in a workshop with the people responsible for the service, since its value lies as much in the shared understanding it creates as in the finished diagram (Grimes, 2019).

Whose perspective should shape the map follows the same logic. A journey map should represent one specific user or persona; mapping more than one audience in a single diagram blurs the narrative and weakens the insight (Gibbons, 2018). A blueprint needs a wider group: a knowledge holder for every stage and layer of delivery, including frontstage and backstage staff, and departments such as customer support, marketing and senior leadership that are too often left out (Gibbons and Kendrick, 2019). An ecosystem map calls for people with strategic ownership across the service, since the aim is to see how the pieces connect rather than the specialist detail of any one part (Grimes, 2019). Government Digital Service (2017) guidance adds a practical check that applies to any of the three: once a draft map exists, show it to people who observed the research and the teams who deliver the service, and revise it until they agree it reflects reality.

In practice, the approaches build on one another rather than compete. An ecosystem map can scope where more detailed mapping is needed, a journey map can then build empathy for a specific part of that ecosystem, and a blueprint can turn the resulting insight into an operational fix (Grimes, 2019; Gibbons and Kendrick, 2019). The right starting point depends on the question being asked, not on which map happens to be most familiar.