Vegetarian Dishes That Sell as Well as Steak
We spent a quarter trying to get food right, and the useful lessons were not the ones we expected.
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.
Where to start on Monday
The first thing to establish is what you are actually optimising for. 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 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.
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. In practice the answer showed up in the calendar before it showed up in the dashboard.
The habit that compounds
Consider the failure mode rather than the success case. 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 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. 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. 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.
The quiet win
Most of the difficulty lives at the boundaries, not in the middle. 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.
Consistency is worth more than any individual improvement to food. 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.
Begin with the obvious one
There is a version of food that is mostly ritual. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. When we mapped it out, four of the seven steps existed only to compensate for the second one.
What looks like a process problem is frequently an ownership problem. 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 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. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
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
The advice worth ignoring
Nobody gets credit for the work that did not need doing. 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 shared definition of "done" removes more friction than any tool. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.
The one that only matters at scale
It helps to separate the decision from the execution. 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.
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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
The checklist we ended up with:
- Decide in advance what would make you stop
- Name one person accountable — not a group
- Prefer the reversible option when the evidence is thin
The expensive mistake
Speed and reversibility are the trade-off worth naming out loud. 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.
The expensive mistakes here are rarely the technical ones. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
What to do first
Scope is the variable everyone adjusts last and should adjust first. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. 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. 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 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. The evidence here is thinner than anyone quoting it tends to admit.
The one people skip
Feedback loops shorter than the planning cycle change everything. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. That said, none of this generalises cleanly across team sizes.
What looks like a process problem is frequently an ownership problem. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.
Where to start on Monday
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. A useful test: if this disappeared tomorrow, how long before anyone noticed?
The tooling question is downstream of the constraint question. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. Set a date at which you will stop, and write down in advance what would make you stop earlier.
The habit that compounds
A shared definition of "done" removes more friction than any tool. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
Consistency is worth more than any individual improvement to food. 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 quiet win
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. The evidence here is thinner than anyone quoting it tends to admit.
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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
Documentation is a symptom: you write it where the design is unclear. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. It is worth saying that we have not run this long enough to be confident.
The short version: decide what you are optimising for, write it down, and revisit it when the answer stops feeling obvious.