Some Friction Provides Necessary Confirmation
When simplifying a process, treating every step as an obstacle can remove necessary checks and undermine trust.

In experience design, packing multiple benefits into a single moment often leaves people unable to recall which promise is being fulfilled. A more reliable approach is to deliver one promise per moment and record that choice in a moment card.

The first thing to stop is packing multiple benefits into a single moment. In experience design, letting claims accumulate leaves people unable to recall which promise is being fulfilled.
Very little may need to remain. Keeping less makes it possible to deliver one promise per moment.
Deliver one promise per moment. Until that happens, the approach still amounts to packing multiple benefits into a single moment.
Clarity often slips through well-intentioned additions. To accommodate more situations, teams rewrite the promise until it once again bundles multiple benefits into a single moment.
Every addition makes the boundaries harder to enforce unless the team returns to the underlying problem: people cannot recall which promise is being fulfilled.
An exclusion list is more useful than a string of adjectives. Define when the promise must not be used, so the team understands that “one promise per moment” is a working rule.
Keep the list short enough to read in full during a design review.
The moment card keeps ideas within the agreed boundaries. Ideas that go beyond them can still exist, but they cannot stand in for the promise.
It holds because the experience lead owns it, and has the authority to say no.
When those boundaries are crossed, go beyond correcting the finished work. Return to the moment card and add the condition that was bypassed.
Then review it with the same question: can this moment be explained in a single sentence?
From non-negotiable principles to practical tools, each layer answers one question, keeping the promise from becoming a bundle of benefits packed into a single moment.
This layer defines what is non-negotiable in the promise for a moment.
This layer turns the promise for a moment into criteria that can be checked.
This layer defines what can change when the promise for a moment is applied in different contexts.
This layer puts the promise for a moment in the hands of the people using 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.
Identify the points in experience design where the promise for a moment guides a decision. Start there, before rewriting a bundle of benefits packed into a single moment.
Replace lengthy explanations with a moment card. Keep only what supports the principle of “one promise per moment.”
In design reviews, ask just one question: can this moment be explained in a single sentence? If there is no clear answer, the decision has yet to be made.
The experience lead owns this. Without an owner to maintain it, the promise for a moment will quietly change when priorities conflict.
When simplifying a process, treating every step as an obstacle can remove necessary checks and undermine trust.
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.
When an experience audit treats a complete touchpoint map as the finished result, the map may be comprehensive while leaving everyone unclear about why each touchpoint exists.