What Restaurant Reviews Consistently Get Wrong
We spent a quarter trying to get food right, and the useful lessons were not the ones we expected.
Most teams arrive at food the same way: something breaks, and the fix becomes a habit.
The objection worth taking seriously
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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
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. Set a date at which you will stop, and write down in advance what would make you stop earlier.
How we got here
The compounding effects matter far more than the individual wins. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. 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. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
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 evidence here is thinner than anyone quoting it tends to admit.
Where this leaves us
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 first thing to establish is what you are actually optimising for. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
Nobody gets credit for the work that did not need doing. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
A different reading
The default answer is right often enough to be dangerous. The first quarter shows the intended effect; the second shows what the intended effect displaced.
A shared definition of "done" removes more friction than any tool. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. When we mapped it out, four of the seven steps existed only to compensate for the second one.
The incentive problem
Consistency is worth more than any individual improvement to food. 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. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
What would change our mind
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. This is easier to write than to hold to when a deadline appears.
The interesting constraint is almost never the one in the brief. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
You can have it fast, or you can have it reversible. Pick before you start, not after.
— Overheard in a retrospective
The received wisdom
Measurement is usually where this falls apart. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
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.
A more modest claim
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.
There is a version of food that is mostly ritual. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
What the data actually shows
What looks like a process problem is frequently an ownership problem. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
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. A useful test: if this disappeared tomorrow, how long before anyone noticed?
What we look for now:
- Review the numbers monthly; change the targets rarely
- Keep the feedback loop shorter than the planning cycle
- Write the constraint down before choosing a tool
The objection worth taking seriously
Nobody gets credit for the work that did not need doing. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. The clearest signal was that people stopped asking where things were.
The second-order effects arrive about a quarter after the first-order ones. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. 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. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. It is worth saying that we have not run this long enough to be confident.
How we got here
A shared definition of "done" removes more friction than any tool. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. 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. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
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. That said, none of this generalises cleanly across team sizes.
Where this leaves us
The first thing to establish is what you are actually optimising for. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.
It helps to separate the decision from the execution. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.
Measurement is usually where this falls apart. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
A different reading
Feedback loops shorter than the planning cycle change everything. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. Set a date at which you will stop, and write down in advance what would make you stop earlier.
The expensive mistakes here are rarely the technical ones. 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.
None of this generalises perfectly. Take the parts that map onto your constraints and discard the rest — that is what the framing is for.