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