A drink standard that survives a new barista
A recipe written as “to taste” only works with its author. Here is what a drink standard consists of when it has to be handed to a new person without losing the result.
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 is rarely enough: beans change between batches and grind settings shift during the day. A recipe therefore needs an operating range and an adjustment order approved by the product owner, not a universal instruction such as “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, and a self-report of “all fine” is not enough. The next step is regular independent tasting against defined criteria. Until that loop operates systematically, we do not use it as evidence of drink consistency.
What a standard does not solve
A standard does not make a person attentive and does not replace training. It gives the team a shared language for reviewing the result and finding the source of a deviation. Pace, attention and working through a queue remain matters of training and mentoring.
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.