Ghost Kitchens and the Future of Delivery

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

The one people skip

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. It is worth saying that we have not run this long enough to be confident.

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.

Where to start on Monday

It helps to separate the decision from the execution. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. That said, none of this generalises cleanly across team sizes.

There is a version of food that is mostly ritual. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. When we mapped it out, four of the seven steps existed only to compensate for the second one.

The habit that compounds

A shared definition of "done" removes more friction than any tool. 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. There are organisations where the opposite is true, and they are not obviously worse off.

Documentation is a symptom: you write it where the design is unclear. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

Scope is the variable everyone adjusts last and should adjust first. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. Set a date at which you will stop, and write down in advance what would make you stop earlier.

The expensive mistake

Consistency is worth more than any individual improvement to food. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.

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. The evidence here is thinner than anyone quoting it tends to admit.

What to do first

Feedback loops shorter than the planning cycle change everything. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The clearest signal was that people stopped asking where things were.

What looks like a process problem is frequently an ownership problem. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.

Nobody gets credit for the work that did not need doing. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. This is easier to write than to hold to when a deadline appears.

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 quiet win

The default answer is right often enough to be dangerous. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. 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. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.

Begin with the obvious one

Measurement is usually where this falls apart. 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?

Consider the failure mode rather than the success case. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. The version of this that works fits on an index card. The version that fails needs an onboarding session.

The second-order effects arrive about a quarter after the first-order ones. 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 one that only matters at scale

The interesting constraint is almost never the one in the brief. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

The tooling question is downstream of the constraint question. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

The advice worth ignoring

Most of the difficulty lives at the boundaries, not in the middle. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.

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

What we look for now:

• Prefer the reversible option when the evidence is thin
• Decide in advance what would make you stop
• Keep the feedback loop shorter than the planning cycle
• Agree on what "done" means, in writing, before starting
• Write the constraint down before choosing a tool

The one people skip

The expensive mistakes here are rarely the technical ones. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. Set a date at which you will stop, and write down in advance what would make you stop earlier.

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. When we mapped it out, four of the seven steps existed only to compensate for the second one.

Where to start on Monday

The compounding effects matter far more than the individual wins. 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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

The tooling question is downstream of the constraint question. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.

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

The habit that compounds

Scope is the variable everyone adjusts last and should adjust first. 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.

What looks like a process problem is frequently an ownership problem. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

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 expensive mistake

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.

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