Part 2 of 2. Part 1 — Why Your Staff Won’t Deliver Consistent Service argued that inconsistent service is a system failure, not a personal one. The necessary steps brings things in order are the defining the standards, having that meaningful briefing and following up with a debriefing to ensure everything is followed through.
- Standard — defined
- Briefed — activated
- Debriefed — corrected
Layer 1: Does a standard exist that someone actually wrote down?
Every service interaction already follows a structure, whether you designed it or not. The only question is whether that structure has been written down and trained, or whether each person is running a private version of it. This is the base layer, and without it nothing above it holds.
The specific failure worth naming is that the standard usually exists, and it is usually out of date. A business writes its standards when it opens, then lets them sit, while the customer profile shifts and new failure points appear. The standard stays frozen at a moment that no longer exists.
In aviation, standards are route-specific. What works on a long-haul European service is not what works on a regional service into the subcontinent; what counts as attentive differs. The standard adapts to the customer, never the reverse. And it is never finished as every complaint logged, every edge case encountered feeds back into it.
A static standard is a liability. A living one is an advantage.
When did you last update yours?
Layer 2: What activates the standard on the day?
A written standard that nobody reads on the morning of the shift is a document, not a system. This is where almost every business stops, and it is also the cheapest layer to build. The briefing is what converts a standard into behaviour, remember it is not a meeting, and not a huddle where a manager reads yesterday’s numbers aloud, but five minutes before the doors open, answering three questions:
- What is different today? The large booking, the staff shortage, the delivery that did not arrive.
- Who needs extra attention? Last week’s complaint returning. The first-time customer.
- What are we watching for? The one failure point most likely to bite today.
That is it. Five minutes. Earlier when my team had the fifteen minutes where one person reading the list, the other checking her watch this was not a briefing. Nobody had defined what should happen in them, so one person filled them with preparation and the other filled them with waiting.
Both behaved rationally; only one had been given a reason.
A standard tells your team what good looks like. A briefing tells them what today looks like.
You need both, and you need the second one daily. I will come back to how the best operators run this briefing in a later piece.
Layer 3: What corrects the drift?
Standards decay. Not dramatically but quietly, a few degrees at a time, until the written version and the practised version are different documents. The debrief is what catches that.
Ten minutes at the end of the shift, on three questions:
- What went differently from how we planned it?
- What did a customer need that our standard did not cover?
- What do we change before tomorrow?
Question two is the valuable one; it is the only reliable way a standard learns. Every gap your team improvised around today is tomorrow’s missing line, and improvisation is the signal, not the failure. Most businesses run this only after something goes badly wrong, which is precisely when defensiveness makes it useless. Run it when nothing went wrong and it becomes information instead of blame.
The debrief is where the loop closes. Without it, layer one goes stale and layer two repeats yesterday’s assumptions.
This is also the layer that makes recovery possible when something does break. Recovery has three layers of its own, and deserves its own piece.
What about judgment?
A fair challenge: does this not turn people into scripts? The opposite, in practice. No standard anticipates every customer especially the person holding themselves together after bad news, the loyal customer who has quietly reached their limit. What your team does in those moments is the difference between a customer who feels rescued and one who writes a review.
But judgment only becomes available once the stack is solid. When the standard is trustworthy and the briefing is current, your team stops spending attention on remembering the process and starts spending it on the person in front of them.
The system does not replace judgment. It frees it.
What should you do in the next seven days?
Three actions. None require a consultant or a budget.
Days 1–2 — Audit one interaction end to end. Pick your most common one: an enquiry, a complaint, a first purchase. Does a written step exist for every stage? If your best person is off sick tomorrow, would the cover know what to do?
Days 3–4 — Check the date on it. If it predates your current customer profile, it is already misaligned with the service you need today.
Days 5–7 — Ask your team one question. “What is the one situation where you are never sure what to do?”
That answer is your next standard, because the edge cases your team improvises around are exactly where customers are most likely to remember how they were treated. Then run one five-minute briefing and one ten-minute debrief, and see what surfaces.
Build the standard first. Brief it daily. Debrief it honestly. In that order, every time.
The architecture your team deserves
Consistent service is not a personality trait. It is not something you hire your way to, and it does not arrive after a motivational speech.
It is architecture.
The people you hired, who in most cases, do care and are trying, deserve to work inside a system that gives them a genuine chance to succeed. The question was never whether your staff care; they probably do.
The question is whether you have built the architecture that lets them show it.
Next in this series: what this architecture looks like in an environment where every detail has been designed on purpose.
Running this audit and not liking what you find? Book a CX conversation — an hour, no pitch, and you leave with the three gaps worth closing first.