Design recovery into the journey; don't improvise it
In service blueprints, if recovery design still covers only the happy path, the result is often that when something goes wrong, staff improvise and the experience varies from person to person.
Insight Series Experience & Interaction Finance
Give Every Touchpoint a Purpose, or the Map Is Just an Inventory
In an experience audit, treating a touchpoint map as complete once every touchpoint is plotted often produces a comprehensive diagram that leaves no one clear on why each point exists. A stronger approach is to label every touchpoint with the single outcome it should help achieve, making its purpose explicit.
Key points
- In an experience audit, a touchpoint map should do more than show every point of contact.
- Otherwise, the same problem keeps returning: the map is complete, but no one knows why each touchpoint exists.
- Start instead by giving every touchpoint one clear purpose: the outcome it is meant to bring about.
- Record those decisions as purpose annotations, owned by the experience lead.
- Then judge the map by one question: if touchpoints with no clear purpose were removed, would the journey become clearer?
01How Touchpoint Maps Translate into Practice
Putting a touchpoint map in a document is not the same as making it useful in an experience audit. The first step is to give every touchpoint one clear purpose.
If that translation merely shortens the instruction to ‘map every touchpoint,’ frontline teams face the same problem: the map is complete, but no one knows why each point exists.
Give every touchpoint one clear purpose. Until that happens, the map is still just an exercise in plotting every point of contact.
02Where Touchpoint Maps Get Distorted
Touchpoint maps most often lose their shape when work is divided up. Each department takes away a phrase it can repeat, but not the corresponding reasons to say no.
The result still looks like a complete touchpoint map from the outside. Internally, no one can explain why each point exists.
03The Smallest Usable Unit of a Touchpoint Map
The smallest useful unit of a touchpoint map is not a whole manual. It is a judgment someone can make on the spot. A purpose annotation should serve that role.
Frontline teams should not have to guess what the brand team would think when they use the touchpoint map.
04The Touchpoint Map Frontline Teams Receive
At the end of the audit, check one real-world instance: have the purpose annotations slipped back into a simple exercise in mapping every touchpoint?
Revision is not necessarily a problem. The problem is revising the map without acknowledging that it has changed.
05Where Does the Judgment in a Touchpoint Map Belong?
Judgment must stay with the people using the map. The experience lead owns it, while teams on the ground have the authority to reject touchpoints on the basis of their stated purpose.
At the end of training, ask just one question: would removing touchpoints with no clear purpose make the journey clearer?
Framework
The Four Layers of a Touchpoint Map
From non-negotiable principles to tools teams can use on the ground, each layer answers one question. This keeps the touchpoint map from becoming another exercise in mapping every point of contact.
L1Purpose
This layer defines what cannot be compromised in the touchpoint map.
L2No purpose
This layer turns the touchpoint map into criteria that can be checked.
L3Retention
This layer sets out what may change across different contexts.
L4Remove
This layer puts the touchpoint map in users’ hands and defines the exceptions.
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 when the touchpoint map is actually used in an experience audit. Do not begin by rewording the instruction to map every point of contact.
Action 02
Keep it to one page
Use purpose annotations instead of longer explanations. Keep only what helps give each touchpoint one clear purpose.
Action 03
Judge it by one question
At the end of the audit, ask only: would removing touchpoints with no clear purpose make the journey clearer? If you cannot answer, you have not made a decision.
Action 04
Name the owner
The experience lead owns the map. Without an owner, it will be quietly rewritten when priorities conflict.
Related
All insightsRelated insights
Assess Both Touchpoint Coverage and Depth
In diagnostic projects, if touchpoint audits still only check whether a touchpoint exists, the result is often touchpoints that are present but not deep enough to influence decisions.
Be Prepared to Remove Low-Value Touchpoints
When experience improvements only add touchpoints, people face more distractions while the moments that matter lose impact.