The Art of Restaurant Photography

Most teams arrive at food the same way: something breaks, and the fix becomes a habit.

Where it still breaks

Most of the difficulty lives at the boundaries, not in the middle. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. There are organisations where the opposite is true, and they are not obviously worse off.

Scope is the variable everyone adjusts last and should adjust first. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

The part that surprised us

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 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.

Nobody gets credit for the work that did not need doing. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. A useful test: if this disappeared tomorrow, how long before anyone noticed?

What changed

The compounding effects matter far more than the individual wins. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. It is worth saying that we have not run this long enough to be confident.

The second-order effects arrive about a quarter after the first-order ones. The first quarter shows the intended effect; the second shows what the intended effect displaced. The version of this that works fits on an index card. The version that fails needs an onboarding session.

Speed and reversibility are the trade-off worth naming out loud. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.

How we knew it was working

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.

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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

What we tried first

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

Documentation is a symptom: you write it where the design is unclear. 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 clearest signal was that people stopped asking where things were.

Feedback loops shorter than the planning cycle change everything. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.

The bottleneck is never where you think it is — that is what makes it a bottleneck.

— Overheard in a retrospective

What it cost

Consider the failure mode rather than the success case. 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.

The tooling question is downstream of the constraint question. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.

It helps to separate the decision from the execution. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

The checklist we ended up with:

• Write the constraint down before choosing a tool
• Review the numbers monthly; change the targets rarely
• Agree on what "done" means, in writing, before starting

What we would do differently

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

Measurement is usually where this falls apart. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. This is easier to write than to hold to when a deadline appears.

What looks like a process problem is frequently an ownership problem. 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 numbers

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

Measurement is usually where this falls apart. 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. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The evidence here is thinner than anyone quoting it tends to admit.

The situation

The default answer is right often enough to be dangerous. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

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. There are organisations where the opposite is true, and they are not obviously worse off.

Where it still breaks

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. Set a date at which you will stop, and write down in advance what would make you stop earlier.

It helps to separate the decision from the execution. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.

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

The part that surprised us

Most of the difficulty lives at the boundaries, not in the middle. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. That said, none of this generalises cleanly across team sizes.

The interesting constraint is almost never the one in the brief. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.

There is a version of food that is mostly ritual. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.

What changed

What looks like a process problem is frequently an ownership problem. 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. When we mapped it out, four of the seven steps existed only to compensate for the second one.

We will revisit this once we have another two quarters of data. The current answer feels right, which is exactly when it is worth checking.