A drink standard that survives a new barista

A good drink is the result of a dozen decisions, most of them made in seconds. The question is not whether a particular barista can make them, but whether the next person on the next shift will repeat them.

Parameters instead of adjectives

“Rich but not bitter” does not transfer. Numbers do: grind, dose, yield, extraction time, water and milk temperature. Words stay in the description of the goal, but execution relies on parameters visible on the scale and the timer.

Ranges, not points

A single exact value makes a poor standard: beans change between batches, humidity and grind drift during the day. So each parameter gets a range and a rule for what to do when it is exceeded: adjust the grind, not the time; change the basket, not the pressure.

• The range is what a shift works inside without asking anyone.
• Leaving the range triggers a described action, not improvisation.
• Leaving the range repeatedly is a signal that travels above the shift — to purchasing or production.

Tasting as measurement

Numbers do not replace taste, but a self-report of “all fine” is not a check. We use blind tasting: the person evaluates a drink without knowing whose shift or which batch it is. That is the only way to separate quality from politeness towards a colleague.

“If a check cannot be run without trusting the person being checked, it is not a check.”

What a standard does not solve

A standard does not make a person attentive and does not replace training. It reduces variance between people and gives a shared language for discussing the result. Everything to do with pace, attention and behaviour in a queue stays with training and mentoring — a separate, unsolved task.