Use the same promise from online to on-site
When the online-to-store handoff repeats everything already covered online, people often feel they are starting all over again.
Article Experience & Interaction Education
Write service standards as principles, so the front line can adapt
When writing service standards, reception principles often still take the form of long step-by-step checklists, and the moment the situation changes, the checklist stops working. A more robust approach is to distil the standard into a few adaptable principles and lock that choice in with a principle card.
Key points
- In writing service standards, reception principles should no longer remain long step-by-step checklists.
- Left unaddressed, the same thing keeps happening: the moment the situation changes, the checklist stops working.
- Start somewhere else instead: distil the standard into a few adaptable principles.
- Record the choice on a principle card, owned by the service lead.
- From then on, test against one question only: when the situation changes, can staff handle it using principles rather than memorized steps?
01Where reception principles get stuck
In writing service standards, reception principles are usually written as long step-by-step checklists. Everyone nods along because they haven't yet hit the real problem: the moment the situation changes, the checklist stops working.
The meeting ends quickly. Once the people who actually use the reception principles leave the room, all they're left with is this: the moment the situation changes, the checklist stops working.
Distil the standard into a few adaptable principles. Until that happens, reception principles remain stuck as long step-by-step checklists.
02The real sticking point
The sticking point isn't the writing. A long checklist can explain many situations, yet it can't prevent this: the moment the situation changes, the checklist stops working.
When more people demand answers from the reception principles at once, they only grow more abstract, and the old problem returns to the table: the moment the situation changes, the checklist stops working.
03Redefining reception principles
A more useful starting point is to distil the standard into a few adaptable principles. Only once what's ruled out is spelled out do reception principles start carrying real choices.
Keep the long checklist and the language may read more smoothly, but the problem remains: the moment the situation changes, the checklist stops working.
04Turning reception principles into a tool
Write this starting point up as a principle card. For reception principles, this one page is more useful than yet another, longer explanation.
In training, refer only to the principle card. Don't reinvent a reception principle in every discussion.
05Who maintains reception principles
Ownership must sit with a specific person: the service lead. Reception principles without an owner get rewritten at the first conflict.
Acceptance comes down to one question: when the situation changes, can staff handle it using principles rather than memorized steps? If there's no answer, the reception principles aren't a decision yet.
Framework
The four layers of reception principles
From what is non-negotiable to tools usable on the ground, each layer answers a single question, so reception principles don't get rewritten into long step-by-step checklists.
L1Principles
This layer states what in the reception principles is non-negotiable.
L2Fixed actions
This layer distils reception principles into checkable conditions.
L3What can flex
This layer defines what reception principles can flex across different contexts.
L4Escalation
This layer hands reception principles to the people who use them, with exceptions spelled out.
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 writing service standards, mark the moments when reception principles are actually called upon. Don't start by rewriting the long step-by-step checklist.
Action 02
Keep it to one page
Replace longer explanations with the principle card, keeping only what supports “distilling the standard into a few adaptable principles.”
Action 03
Judge it by one question
In training, ask only: when the situation changes, can staff handle it using principles rather than memorized steps? If there's no answer, it isn't a decision yet.
Action 04
Name the owner
Owner: the service lead. Reception principles without an owner get quietly rewritten in the face of conflict.
Related
All insightsRelated insights
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.
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.