Inside a Michelin Kitchen at Six in the Morning

The interesting thing about food is how rarely the hard part is the part everyone prepares for.

The received wisdom

Feedback loops shorter than the planning cycle change everything. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.

Documentation is a symptom: you write it where the design is unclear. The first quarter shows the intended effect; the second shows what the intended effect displaced. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

How we got here

The compounding effects matter far more than the individual wins. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The evidence here is thinner than anyone quoting it tends to admit.

Scope is the variable everyone adjusts last and should adjust first. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.

Measurement is usually where this falls apart. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.

What would change our mind

It helps to separate the decision from the execution. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. In practice the answer showed up in the calendar before it showed up in the dashboard.

The second-order effects arrive about a quarter after the first-order ones. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. This is easier to write than to hold to when a deadline appears.

The tooling question is downstream of the constraint question. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.

Where this leaves us

The default answer is right often enough to be dangerous. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.

Most of the difficulty lives at the boundaries, not in the middle. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. Set a date at which you will stop, and write down in advance what would make you stop earlier.

The first thing to establish is what you are actually optimising for. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. There are organisations where the opposite is true, and they are not obviously worse off.

What the data actually shows

Consider the failure mode rather than the success case. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. The version of this that works fits on an index card. The version that fails needs an onboarding session.

What looks like a process problem is frequently an ownership problem. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

Speed and reversibility are the trade-off worth naming out loud. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.

A different reading

There is a version of food that is mostly ritual. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. When we mapped it out, four of the seven steps existed only to compensate for the second one.

A shared definition of "done" removes more friction than any tool. The things that are easy to count are rarely the things that matter, and once a number reaches a dashboard it starts shaping behaviour whether or not it deserves to.

The cost of a bad decision is rarely the decision. It is the six months of building on top of it.

— Overheard in a retrospective

A more modest claim

The expensive mistakes here are rarely the technical ones. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.

The interesting constraint is almost never the one in the brief. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.

The checklist we ended up with:

1. Decide in advance what would make you stop
2. Prefer the reversible option when the evidence is thin
3. Review the numbers monthly; change the targets rarely

The incentive problem

Nobody gets credit for the work that did not need doing. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. A useful test: if this disappeared tomorrow, how long before anyone noticed?

Consistency is worth more than any individual improvement to food. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

The first thing to establish is what you are actually optimising for. The first quarter shows the intended effect; the second shows what the intended effect displaced. The clearest signal was that people stopped asking where things were.

The objection worth taking seriously

The interesting constraint is almost never the one in the brief. The things that are easy to count are rarely the things that matter, and once a number reaches a dashboard it starts shaping behaviour whether or not it deserves to. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

Feedback loops shorter than the planning cycle change everything. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.

What looks like a process problem is frequently an ownership problem. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.

The received wisdom

The expensive mistakes here are rarely the technical ones. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. That said, none of this generalises cleanly across team sizes.

Measurement is usually where this falls apart. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.

Consistency is worth more than any individual improvement to food. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

How we got here

Scope is the variable everyone adjusts last and should adjust first. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.

The compounding effects matter far more than the individual wins. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.

What would change our mind

Speed and reversibility are the trade-off worth naming out loud. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. The version of this that works fits on an index card. The version that fails needs an onboarding session.

The tooling question is downstream of the constraint question. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. In practice the answer showed up in the calendar before it showed up in the dashboard.

Where this leaves us

It helps to separate the decision from the execution. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

We will revisit this once we have another two quarters of data. The current answer feels right, which is exactly when it is worth checking.