Fifteen minutes before first service, I watched two members of my team prepare for the same shift in completely different ways. Same training. Same manual. Six months apart in experience, no more. Both had their section ready early. Neither of them looked rushed. Then one of them picked up the passenger list.
She read it properly. She noticed the two parents on their own with small children who would need checking on. The wellbeing request. The person meeting family for a reason nobody had written down but anyone could guess. Each one a different situation, each needing something slightly different from us. Then she asked me one question: who gets looked after first?
The other one checked her watch.
Neither of them was a better person. Neither of them cared more than the other. The difference happened in those fifteen minutes — and it happened because nobody had ever made those fifteen minutes mean anything.
If your service quality changes depending on who is working, you do not have a training problem or a hiring problem. You have a system that was never built. Consistent customer service runs on three layers working together: a standard that is written down, a briefing that activates it daily, and a debrief that corrects it when it drifts. Most businesses build the first layer, skip the other two, and then blame the people.
Why does service quality change from shift to shift?
Most businesses only discover how good their service really is at the moment a customer is already unhappy — and if nobody with any authority is present, that moment gets worse quickly. The usual band-aid is to keep someone capable on the floor who can listen, report it upward, and trigger some kind of investigation.
But ask your team how a complaint should be handled, and you will get one of three answers. What they personally think is right. What a manager told them once, two years ago, half-remembered. Or that they use their judgement and hope. None of those is a standard. All of them are improvisations.
Multiply that improvisation across three people and ten shifts and you produce exactly the pattern already sitting in your reviews: uneven, occasionally excellent, frequently not. Your customers are not experiencing your business. They are experiencing whoever happened to be working that day.
That is a lottery. It is not a service model.
And it compounds quietly. The customer who got the good version tells nobody, because service that works is invisible — there is no story in it. The one who got the other version tells everyone, and leaves a review that reads like a verdict on the whole business. You are not being judged on your average. You are being judged on your worst shift, by the person least inclined to give you a second attempt.
Why doesn’t hiring “people people” fix it?
“If they cared about the job, they would figure it out.”
In fairness, motivation does drive performance. But even the most motivated person needs a lane to run in, especially at the start. Nobody performs well inside uncertainty — and the more someone cares, the more that uncertainty costs them. What a written standard gives them is the ability to know, before a single customer arrives, what happens when someone becomes unwell and how a dietary requirement gets flagged.
Motivation is the prerequisite. The system is the mechanism.
Someone who genuinely cares but has no clear standard still works from their own private interpretation of what good looks like. So does everyone else on your team. Each interpretation differs slightly. That difference, multiplied across every interaction, is the inconsistency you are trying to fix. Caring is necessary. It is nowhere near sufficient.
So what do you actually build?
Three layers are required to build a consistent experience for the customer. A standard that is written down and kept current. A briefing that activates it on the day. A debrief that catches the drift before it hardens into the new normal.
Most businesses build the first and stop there. Which is precisely why the other two are where the advantage sits — they are the cheapest layers to build and almost nobody builds them.
You will expect roadblocks at this junction. There are none. This requires no consultant, no budget, and no new software. The standard is a document you already have. The briefing is five minutes. The debrief is ten. What they require is somebody deciding they are not optional — which is the only part of this that has ever been difficult.
In the next post, I have explained what is the consistency stack and how it looks in real, what the specifics to watch for and let’s plan it together.
Recognise your operation in any of this? Book a CX conversation — an hour, no pitch, and you leave with the three gaps worth closing first.