Street Food Markets Are Reinventing Fine Dining

Ask ten people to define food and you will get ten answers, most of them describing a symptom rather than the thing itself.

Putting it together

The interesting constraint is almost never the one in the brief. 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.

The compounding effects matter far more than the individual wins. 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 tooling question is downstream of the constraint question. The first quarter shows the intended effect; the second shows what the intended effect displaced. Set a date at which you will stop, and write down in advance what would make you stop earlier.

The short version

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

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

What it is not

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.

Most of the difficulty lives at the boundaries, not in the middle. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.

Where to go deeper

It helps to separate the decision from the execution. 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. 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.

How it works

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. In practice the answer showed up in the calendar before it showed up in the dashboard.

Consider the failure mode rather than the success case. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. A useful test: if this disappeared tomorrow, how long before anyone noticed?

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

— Overheard in a retrospective

Why it is confusing

The second-order effects arrive about a quarter after the first-order ones. 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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

Measurement is usually where this falls apart. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.

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.

A common misreading

Nobody gets credit for the work that did not need doing. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. This is easier to write than to hold to when a deadline appears.

There is a version of food that is mostly ritual. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.

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

The checklist we ended up with:

1. Name one person accountable — not a group
2. Agree on what "done" means, in writing, before starting
3. Keep the feedback loop shorter than the planning cycle
4. Prefer the reversible option when the evidence is thin

The edge cases

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

The first thing to establish is what you are actually optimising for. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.

The vocabulary problem

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

The compounding effects matter far more than the individual wins. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.

Putting it together

The tooling question is downstream of the constraint question. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. 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. 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.

The short version

Consider the failure mode rather than the success case. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. When we mapped it out, four of the seven steps existed only to compensate for the second one.

The default answer is right often enough to be dangerous. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. It is worth saying that we have not run this long enough to be confident.

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. The version of this that works fits on an index card. The version that fails needs an onboarding session.

What it is not

Scope is the variable everyone adjusts last and should adjust first. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. 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. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. In practice the answer showed up in the calendar before it showed up in the dashboard.

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

None of this generalises perfectly. Take the parts that map onto your constraints and discard the rest — that is what the framing is for.