Farm to Table Is Harder Than It Looks

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

What we would do differently

It helps to separate the decision from the execution. The first quarter shows the intended effect; the second shows what the intended effect displaced.

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.

How we knew it was working

The expensive mistakes here are rarely the technical ones. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. It is worth saying that we have not run this long enough to be confident.

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

There is a version of food that is mostly ritual. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. There are organisations where the opposite is true, and they are not obviously worse off.

The numbers

Speed and reversibility are the trade-off worth naming out loud. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.

Most of the difficulty lives at the boundaries, not in the middle. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

The first thing to establish is what you are actually optimising for. 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.

What it cost

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

The situation

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

Documentation is a symptom: you write it where the design is unclear. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.

Simplicity is not the absence of work. It is the result of it.

— Overheard in a retrospective

What changed

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.

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.

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

Where it still breaks

A shared definition of "done" removes more friction than any tool. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.

Feedback loops shorter than the planning cycle change everything. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.

What we look for now:

• Agree on what "done" means, in writing, before starting
• Name one person accountable — not a group
• Review the numbers monthly; change the targets rarely
• Write the constraint down before choosing a tool

The part that surprised us

The default answer is right often enough to be dangerous. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

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

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

What we tried first

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

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.

What we would do differently

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.

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. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.

How we knew it was working

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

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 numbers

A shared definition of "done" removes more friction than any tool. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.

Feedback loops shorter than the planning cycle change everything. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.

Consistency is worth more than any individual improvement to food. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. Set a date at which you will stop, and write down in advance what would make you stop earlier.

What it cost

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. 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. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. The evidence here is thinner than anyone quoting it tends to admit.

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?

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.