Write service standards as principles, so the front line can adapt
When service standards are still written as long step-by-step checklists, the checklist tends to break the moment conditions on the ground change.
Insight Series Experience & Interaction Automotive & Mobility
A journey is a series of trade-offs, not a list of touchpoints
When mapping an experience, treating the journey as an exhaustive touchpoint list produces a long inventory with no clear sense of what to leave out. A better approach is to define the journey around a few moments that demand a choice, then record those choices in a trade-off table.
Key points
- When mapping an experience, the journey must move beyond an exhaustive list of touchpoints.
- Leave it unresolved, and the same pattern repeats: a long list with no clear sense of what to leave out.
- Start here: define the journey around a few moments that demand a choice.
- Record those choices in a trade-off table, with the experience lead accountable for upholding them.
- From then on, use one acceptance test: does the table specify which touchpoints to drop, or does it simply list them all?
01Who Owns the Journey?
Without a clear owner, the journey becomes an exhaustive list of touchpoints. Everyone contributes, but no one is accountable for the result: a long list with no clear sense of what to leave out.
Ownership does not mean rewriting every sentence. It means giving someone the authority to keep the journey focused on a few moments that demand a choice, even when priorities clash.
Define the journey around a few moments that demand a choice. Without this, it remains an exhaustive touchpoint list.
02What Must Be Handed Over?
A handover needs more than a conversation. Each stage should pass on the trade-off table to the next, rather than perpetuating an exhaustive list of touchpoints.
Without a shared handover document, each team interprets the journey differently. The same problem reappears between teams: a long list with no clear sense of what to leave out.
03When Should the Journey Be Reviewed?
Set a consistent checkpoint at the end of experience mapping. It takes less attention than waiting for a problem and then holding a retrospective.
When that routine gives way to every last-minute campaign, the journey exists only on launch day.
04How Is the Journey Used?
Keep the table simple to use. Anyone opening it should be able to decide whether the work in front of them should proceed.
If the trade-off table still needs an expert to interpret it, it remains an exhaustive touchpoint list, just in a different format.
05What Counts as Complete?
Sending the work out does not make it complete. The test is whether the table specifies which touchpoints to drop, rather than simply listing them all.
The experience lead is accountable. The trade-off table must remain in place when that person moves on, so the journey endures beyond a single project.
Framework
The Four Layers of a Journey
From non-negotiables to practical tools, each layer answers one question, keeping the journey from reverting to an exhaustive touchpoint list.
L1Moments to Keep
This layer defines what is non-negotiable in the journey.
L2Touchpoints to Drop
This layer turns the journey into criteria that can be checked.
L3Reason
This layer defines which aspects of the journey can change across contexts.
L4Owner
This layer puts the journey into the hands of those who use it and makes exceptions explicit.
Note: This diagram is a conceptual framework. It explains a way of thinking and is not statistical data. Source: Qingmei Future Insights.
Recommended actions
Action 01
Start from the site
Identify the moments in experience mapping when the journey must guide a decision. Start there, rather than reworking an exhaustive touchpoint list.
Action 02
Keep it to one page
Replace lengthy explanations with a trade-off table. Keep only what supports defining the journey around a few moments that demand a choice.
Action 03
Judge it by one question
Once the journey map is complete, ask just one question: does it show which touchpoints to leave out, or does it merely list them all? If the team cannot answer, it has not made a decision.
Action 04
Name the owner
The experience lead owns it. Without an owner, the journey will quietly change whenever priorities conflict.
Related
All insightsRelated insights
Find the Moments That Shape Decisions First
In experience projects, spreading effort evenly across every touchpoint often exhausts resources while leaving the moments that actually shape decisions overlooked.
A journey needs an end-to-end owner, not unowned segments
In cross-functional experiences, if end-to-end ownership still means each team optimizing its own stage, the result is often that no one owns the gaps between stages.