Why we describe a standard before we scale it
A location that works “because of a good manager” cannot be repeated. Here is how we write a shift standard so quality does not depend on one person — and where the approach still fails.
The easiest way to open a good location is to find a strong manager and let them hold everything on personal attention. It works — until you open the second one.
A good manager is not a system
When quality lives in a person’s head, every new location starts from zero. You are not scaling a business, you are looking for another exceptional person — and the supply of those is not something you control.
“If a process only works while a specific person is watching it, we have not built anything yet.”
What we fix and what we leave open
We deliberately do not write down everything. A standard that tries to describe every situation stops being read. So we separate two layers.
- Fixed: everything that changes the guest’s result measurably — grind, dose, temperature, timings, cleaning cycles, opening and closing sequence.
- Left to judgement: tone of the conversation, the order of small tasks in a quiet hour, how to recover from an unusual situation.
- Never left to judgement: food safety, cash discipline, equipment safety.
How we check the difference
A standard exists only if you can tell whether it was followed. For each fixed point there is a way to observe it without trusting a self-report — a measurement, a photo of the state, a log entry, or a blind tasting.
Where it still breaks
Two places, honestly. First, a standard written by one team and handed to another loses the reasoning behind it, and people start following the letter instead of the intent. Second, peak load: when a queue forms, the sequence is the first thing to go. Both are on our list, neither is solved.
This piece reflects the team’s operating experience as of the publication date and is not investment advice. Where quantitative data appears, it carries a definition, period and source.