A journey is a series of trade-offs, not a list of touchpoints
When experience mapping still means listing every touchpoint, the list grows long but never shows what to give up.
Article Experience & Interaction Finance
Find the Moments That Shape Decisions First
In experience projects, when key moments are still handled by spreading effort evenly across every touchpoint, resources often run out while decisions still happen in places no one attended to. A sounder approach is to first mark the few moments that truly shape decisions, and lock that choice in with a moment map.
Key points
- In experience projects, key moments should no longer be handled by spreading effort evenly across every touchpoint.
- Left alone, the same thing keeps happening: resources run out, and decisions still happen where no one was paying attention.
- New starting point: first mark the few moments that truly shape decisions.
- Write the choice into the moment map, owned by the experience lead.
- From then on, sign-off rests on one question: does the change land on a moment that shapes decisions?
01What key moments must stop
The first thing key moments must stop is spreading effort evenly across every touchpoint. In experience projects, language that can’t stop leads straight to this: resources run out, and decisions still happen where no one was paying attention.
What carries on can be very little. Keeping it small is what lets the team hold to marking the few moments that truly shape decisions.
First mark the few moments that truly shape decisions. Until that happens, key moments are still stuck at spreading effort evenly across every touchpoint.
02Where ambiguity in key moments leaks in
Ambiguity usually leaks in through well-meant additions. To cover more situations, people write key moments back into spreading effort evenly across every touchpoint.
Each addition that doesn’t look back at the problem makes the boundaries harder to enforce. The problem is this: resources run out, and decisions still happen where no one was paying attention.
03Start with a negative list for key moments
A negative list is more useful than adjectives. Only by writing down when key moments must not be used does the team know that marking the few moments that truly shape decisions isn’t a slogan.
Keep the list short: short enough to be read in full at project kickoff.
04Using tools to keep key moments in bounds
The moment map exists to stop overreach, not to collect inspiration. Out-of-bounds ideas can exist, but they can’t pass themselves off as key moments.
It holds because the experience lead owns it, and has the authority to say no.
05What to do when key moments overstep
When something oversteps, don’t just fix a single deliverable. Go back to the moment map and add the condition that was bypassed this time.
Then recheck with the same question: does the change land on a moment that shapes decisions?
Framework
The four layers of key moments
From what is non-negotiable to the tools used on the ground, each layer answers just one question, so key moments don’t slide back into spreading effort evenly across every touchpoint.
L1Moments
This layer states what in key moments is non-negotiable.
L2The decisions it shapes
This layer turns key moments into conditions that can be checked.
L3On hold
This layer sets out how key moments may flex across different contexts.
L4Validation
This layer hands key moments to the people who use them, and documents 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
In experience projects, mark the points where key moments actually come into play, rather than starting by reworking “spread effort evenly across every touchpoint.”
Action 02
Keep it to one page
Replace longer explanations with a moment map, keeping only what supports “first mark the few moments that truly shape decisions.”
Action 03
Judge it by one question
At project kickoff, ask only: does the change land on a moment that shapes decisions? If not, it isn’t yet a decision.
Action 04
Name the owner
Experience lead. Key moments without an owner get quietly rewritten when conflicts arise.
Related
All insightsRelated insights
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.
Some Friction Provides Necessary Confirmation
When simplifying a process, treating every step as an obstacle can remove necessary checks and undermine trust.