Be Prepared to Remove Low-Value Touchpoints
When experience improvements only add touchpoints, people face more distractions while the moments that matter lose impact.

In multichannel service, if consistency still means each channel answering in its own way, people tend to get a different answer every time they switch channels. A sounder approach is to write one answer for each high-frequency question, shared across every channel, and lock that choice in with an answer card.

Treat answer consistency as each channel answering its own way, and no system can be built. In multichannel service it has to be broken down; otherwise no one can say where the problem lies: switch channels, and you get a different answer.
Breaking it down isn't about adding complexity. It's so that one shared answer for each high-frequency question can take hold across different layers.
Write one answer for each high-frequency question, shared across every channel. Until that happens, answer consistency remains each channel answering its own way.
The layers of answer consistency need clear interfaces. Only when the layer above defines what's non-negotiable does the layer below know where it can flex.
Without interfaces, every situation reinterprets answer consistency, and channels answering their own way creeps back in through the gaps.
Rules can be executed; samples can only illustrate. If a team only collects finished work it likes, every new situation brings back the old problem: switch channels, and you get a different answer.
That's why an answer card sets out conditions, not a single reference.
The execution layer has to work for everyone, not just experts. Before an answer goes live, check that the answer card still points to one shared answer for each high-frequency question across all channels.
Once the execution layer serves only the experienced, answer consistency reverts to each channel answering its own way, understood by only a few.
When iterating, change the rules, not the name of the principle. Service and brand do this together.
Every round ends with the same question: would two channels give the same answer? If you can answer it, the system is still intact.
From the non-negotiables to tools usable in the field, each layer answers just one question, so answer consistency doesn't slide back into each channel answering its own way.
This layer states what in answer consistency is non-negotiable.
This layer distills answer consistency into checkable conditions.
This layer defines what answer consistency allows to vary across situations.
This layer hands answer consistency to the people who use it, and spells out the exceptions.
Note: This diagram is a conceptual framework. It explains a way of thinking and is not statistical data. Source: Qingmei Future Insights.
In multichannel service, mark the moments when answer consistency is actually called on; don't start by rewriting how each channel answers in its own way.
Use an answer card instead of longer guidelines, keeping only what supports “one shared answer for each high-frequency question across all channels.”
Before an answer goes live, ask only: would two channels give the same answer? If you can't say, it isn't a decision yet.
Service and brand own it together. Answer consistency without an owner gets quietly rewritten whenever conflicts arise.
When experience improvements only add touchpoints, people face more distractions while the moments that matter lose impact.
In experience design, if staff feasibility is still considered only from the customer's side, the result is often a great plan that frontline staff can't deliver.
If an experience review reduces every moment to one overall impression, failures at critical moments can disappear into the average.