Opening Night: A Checklist for New Restaurants
Ask ten people to define food and you will get ten answers, most of them describing a symptom rather than the thing itself.
Most teams arrive at food the same way: something breaks, and the fix becomes a habit.
A common misreading
The first thing to establish is what you are actually optimising for. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
A shared definition of "done" removes more friction than any tool. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next.
The vocabulary problem
Consider the failure mode rather than the success case. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
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 evidence here is thinner than anyone quoting it tends to admit.
The short version
Measurement is usually where this falls apart. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
The second-order effects arrive about a quarter after the first-order ones. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
The compounding effects matter far more than the individual wins. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
Putting it together
Nobody gets credit for the work that did not need doing. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. The clearest signal was that people stopped asking where things were.
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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
The interesting constraint is almost never the one in the brief. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. When we mapped it out, four of the seven steps existed only to compensate for the second one.
The edge cases
Feedback loops shorter than the planning cycle change everything. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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.
Consistency is worth more than any individual improvement to food. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. The version of this that works fits on an index card. The version that fails needs an onboarding session.
What it is not
Speed and reversibility are the trade-off worth naming out loud. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.
Most of the difficulty lives at the boundaries, not in the middle. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.
You can have it fast, or you can have it reversible. Pick before you start, not after.
— Overheard in a retrospective
Why it is confusing
It helps to separate the decision from the execution. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. There are organisations where the opposite is true, and they are not obviously worse off.
There is a version of food that is mostly ritual. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.
The tooling question is downstream of the constraint question. 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.
A few things worth checking before you commit:
- Prefer the reversible option when the evidence is thin
- Name one person accountable — not a group
- Keep the feedback loop shorter than the planning cycle
Where to go deeper
The expensive mistakes here are rarely the technical ones. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.
Scope is the variable everyone adjusts last and should adjust first. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. In practice the answer showed up in the calendar before it showed up in the dashboard.
The first thing to establish is what you are actually optimising for. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
How it works
The default answer is right often enough to be dangerous. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.
Feedback loops shorter than the planning cycle change everything. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.
A common misreading
Speed and reversibility are the trade-off worth naming out loud. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
A shared definition of "done" removes more friction than any tool. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.
The vocabulary problem
The compounding effects matter far more than the individual wins. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. That said, none of this generalises cleanly across team sizes.
Documentation is a symptom: you write it where the design is unclear. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.
The short version
Scope is the variable everyone adjusts last and should adjust first. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
Consistency is worth more than any individual improvement to food. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
Putting it together
The second-order effects arrive about a quarter after the first-order ones. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.
There is a version of food that is mostly ritual. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. This is easier to write than to hold to when a deadline appears.
The edge cases
What looks like a process problem is frequently an ownership problem. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. It is worth saying that we have not run this long enough to be confident.
Consider the failure mode rather than the success case. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. There are organisations where the opposite is true, and they are not obviously worse off.
Nobody gets credit for the work that did not need doing. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
The short version: decide what you are optimising for, write it down, and revisit it when the answer stops feeling obvious.