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