What Actually Makes a Restaurant Menu Profitable

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

Making it stick

Consider the failure mode rather than the success case. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next.

Most of the difficulty lives at the boundaries, not in the middle. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. In practice the answer showed up in the calendar before it showed up in the dashboard.

The first month

The tooling question is downstream of the constraint question. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.

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.

Where teams go wrong

Scope is the variable everyone adjusts last and should adjust first. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.

The expensive mistakes here are rarely the technical ones. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.

Start with the constraints

A shared definition of "done" removes more friction than any tool. The first quarter shows the intended effect; the second shows what the intended effect displaced.

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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.

The second-order effects arrive about a quarter after the first-order ones. 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.

Choosing what to measure

The interesting constraint is almost never the one in the brief. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.

What looks like a process problem is frequently an ownership problem. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

Nobody gets credit for the work that did not need doing. 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 caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

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

— Overheard in a retrospective

Handing it over

Documentation is a symptom: you write it where the design is unclear. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

The first thing to establish is what you are actually optimising for. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.

The setup

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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

It helps to separate the decision from the execution. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.

A worked example

The compounding effects matter far more than the individual wins. 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.

The default answer is right often enough to be dangerous. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.

There is a version of food that is mostly ritual. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.

When to change course

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. That said, none of this generalises cleanly across team sizes.

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. A useful test: if this disappeared tomorrow, how long before anyone noticed?

Making it stick

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.

Speed and reversibility are the trade-off worth naming out loud. 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.

Feedback loops shorter than the planning cycle change everything. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. Set a date at which you will stop, and write down in advance what would make you stop earlier.

The first month

The second-order effects arrive about a quarter after the first-order ones. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.

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

Where teams go wrong

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.

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.

Start with the constraints

It helps to separate the decision from the execution. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. 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. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.

Choosing what to measure

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. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

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. The clearest signal was that people stopped asking where things were.

What we look for now:

• Keep the feedback loop shorter than the planning cycle
• Review the numbers monthly; change the targets rarely
• Decide in advance what would make you stop

Handing it over

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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

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