Seasonal Menus: Planning a Whole Year of Produce
Ask ten people to define food and you will get ten answers, most of them describing a symptom rather than the thing itself.
There is no shortage of advice about food. There is a shortage of advice that survives contact with a real week.
The expensive mistake
Consistency is worth more than any individual improvement to food. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
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. The version of this that works fits on an index card. The version that fails needs an onboarding session.
What to do first
It helps to separate the decision from the execution. The first quarter shows the intended effect; the second shows what the intended effect displaced. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
Speed and reversibility are the trade-off worth naming out loud. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
The one that only matters at scale
The expensive mistakes here are rarely the technical ones. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. This is easier to write than to hold to when a deadline appears.
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. It is worth saying that we have not run this long enough to be confident.
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. When we mapped it out, four of the seven steps existed only to compensate for the second one.
Where to start on Monday
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.
The default answer is right often enough to be dangerous. 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.
The tooling question is downstream of the constraint question. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
Begin with the obvious one
Nobody gets credit for the work that did not need doing. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
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. In practice the answer showed up in the calendar before it showed up in the dashboard.
A shared definition of "done" removes more friction than any tool. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. The evidence here is thinner than anyone quoting it tends to admit.
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 advice worth ignoring
The compounding effects matter far more than the individual wins. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. A useful test: if this disappeared tomorrow, how long before anyone noticed?
Documentation is a symptom: you write it where the design is unclear. 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.
The habit that compounds
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. The clearest signal was that people stopped asking where things were.
Consider the failure mode rather than the success case. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
There is a version of food that is mostly ritual. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. Set a date at which you will stop, and write down in advance what would make you stop earlier.
The checklist we ended up with:
- Keep the feedback loop shorter than the planning cycle
- Decide in advance what would make you stop
- Name one person accountable — not a group
- Write the constraint down before choosing a tool
The quiet win
Feedback loops shorter than the planning cycle change everything. 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 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.
The one people skip
Consistency is worth more than any individual improvement to food. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
The tooling question is downstream of the constraint question. 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.
The expensive mistake
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.
Documentation is a symptom: you write it where the design is unclear. 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.
What to do first
The second-order effects arrive about a quarter after the first-order ones. Food rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
Measurement is usually where this falls apart. The first quarter shows the intended effect; the second shows what the intended effect displaced.
The one that only matters at scale
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.
Nobody gets credit for the work that did not need doing. 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.
There is a version of food that is mostly ritual. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
Where to start on Monday
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.
The short version: decide what you are optimising for, write it down, and revisit it when the answer stops feeling obvious.