Why Every Restaurant Needs a Signature Dish

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

Begin with the obvious one

Documentation is a symptom: you write it where the design is unclear. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. This is easier to write than to hold to when a deadline appears.

Scope is the variable everyone adjusts last and should adjust first. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.

There is a version of food that is mostly ritual. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. When we mapped it out, four of the seven steps existed only to compensate for the second one.

The expensive mistake

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. The version of this that works fits on an index card. The version that fails needs an onboarding session.

Most of the difficulty lives at the boundaries, not in the middle. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.

The quiet win

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. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

The first thing to establish is what you are actually optimising for. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.

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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

The one that only matters at scale

A shared definition of "done" removes more friction than any tool. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. The evidence here is thinner than anyone quoting it tends to admit.

Speed and reversibility are the trade-off worth naming out loud. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.

The expensive mistakes here are rarely the technical ones. 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.

The habit that compounds

Nobody gets credit for the work that did not need doing. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. It is worth saying that we have not run this long enough to be confident.

The interesting constraint is almost never the one in the brief. 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.

The compounding effects matter far more than the individual wins. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. That said, none of this generalises cleanly across team sizes.

Every process is perfectly designed to get the results it gets.

— Overheard in a retrospective

The one people skip

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. Set a date at which you will stop, and write down in advance what would make you stop earlier.

The tooling question is downstream of the constraint question. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

The second-order effects arrive about a quarter after the first-order ones. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.

Where to start on Monday

What looks like a process problem is frequently an ownership problem. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.

Consider the failure mode rather than the success case. The first quarter shows the intended effect; the second shows what the intended effect displaced. It is worth saying that we have not run this long enough to be confident.

The default answer is right often enough to be dangerous. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.

What we look for now:

• Agree on what "done" means, in writing, before starting
• Prefer the reversible option when the evidence is thin
• Name one person accountable — not a group
• Review the numbers monthly; change the targets rarely
• Write the constraint down before choosing a tool

What to do first

Feedback loops shorter than the planning cycle change everything. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.

The expensive mistakes here are rarely the technical ones. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. In practice the answer showed up in the calendar before it showed up in the dashboard.

The advice worth ignoring

The compounding effects matter far more than the individual wins. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. The evidence here is thinner than anyone quoting it tends to admit.

The second-order effects arrive about a quarter after the first-order ones. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. A useful test: if this disappeared tomorrow, how long before anyone noticed?

Begin with the obvious one

Speed and reversibility are the trade-off worth naming out loud. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. 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. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. That said, none of this generalises cleanly across team sizes.

The expensive mistake

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.

It helps to separate the decision from the execution. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. This is easier to write than to hold to when a deadline appears.

The quiet win

The default answer is right often enough to be dangerous. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

There is a version of food that is mostly ritual. 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 one that only matters at scale

The short version: decide what you are optimising for, write it down, and revisit it when the answer stops feeling obvious.