Don't Panic — Service Design and Journey Mapping

Service design is the work of arranging the people, evidence, and processes that deliver an outcome. It exists because a service can have excellent screens and still send a person into a queue, a duplicate form, and an email that arrives after its usefulness has died of old age.

The useful starting point is a journey map. It follows one actor through one scenario, not every possible person through every possible circumstance. Give the actor a goal and expectations. Then arrange the journey into phases. In each phase, show actions, mindsets, emotions, and opportunities. The resulting story is compact enough to discuss, which is fortunate, because the actual service has declined to fit inside anyone's organizational chart.

The map needs research. Interviews expose what people say and need. Analytics expose patterns. Support records expose repeat failures. Staff knowledge exposes constraints. Each source sees only part of the beast. Mark assumptions rather than letting them wear a lanyard marked fact.

When the journey says a person struggles, extend it into a service blueprint. Put customer actions at the top. Add frontstage actions that the person sees. Below the line of visibility, add backstage actions and supporting processes. Include evidence such as forms, emails, and status messages. Now a late confirmation email can lead you to a hidden verification queue instead of a week spent rearranging its greeting.

Keep current state and future state apart. Current state reports what happens, including workarounds and friction. Future state proposes what should happen. A proposal only counts when its needed process, policy, data, and staff changes have somewhere to land. Otherwise it is a wish with unusually neat boxes.

Use an experience map for a broad human activity. Use a service landscape when the whole problem crosses services or organizations. Use a user-story map when you are planning features and releases. Similar-looking rectangles have committed many crimes against clarity.

The Double Diamond helps place the work. Discover expands evidence. Define focuses the problem. Develop explores responses. Deliver tests and implements them. Mapping usually starts early, then returns whenever the service or its evidence changes.

Read the Intro for the full set of map types and limits. Use Slides when you need the relationships at a glance. Keep the Cheatsheet nearby while choosing layers and lines. The Practice Reference turns the ideas into a working sequence. Field Notes covers the costs that appear after the workshop has packed up its sticky notes.