Wine Pairing Without the Pretension

We spent a quarter trying to get food right, and the useful lessons were not the ones we expected.

How it works

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

A shared definition of "done" removes more friction than any tool. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

What it is not

Consistency is worth more than any individual improvement to food. 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. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. Set a date at which you will stop, and write down in advance what would make you stop earlier.

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.

The vocabulary problem

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

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

Most of the difficulty lives at the boundaries, not in the middle. 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.

The short version

Scope is the variable everyone adjusts last and should adjust first. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. A useful test: if this disappeared tomorrow, how long before anyone noticed?

Measurement is usually where this falls apart. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

Why it is confusing

The interesting constraint is almost never the one in the brief. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

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

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.

A common misreading

The tooling question is downstream of the constraint question. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. The clearest signal was that people stopped asking where things were.

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

Documentation is a symptom: you write it where the design is unclear. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.

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 checklist we ended up with:

• Prefer the reversible option when the evidence is thin
• Keep the feedback loop shorter than the planning cycle
• Write the constraint down before choosing a tool
• Decide in advance what would make you stop
• Name one person accountable — not a group

The edge cases

The expensive mistakes here are rarely the technical ones. The first quarter shows the intended effect; the second shows what the intended effect displaced. This is easier to write than to hold to when a deadline appears.

The second-order effects arrive about a quarter after the first-order ones. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. It is worth saying that we have not run this long enough to be confident.

The compounding effects matter far more than the individual wins. 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.

Putting it together

The default answer is right often enough to be dangerous. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.

Feedback loops shorter than the planning cycle change everything. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

Where to go deeper

The tooling question is downstream of the constraint question. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.

Consistency is worth more than any individual improvement to food. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

How it works

Scope is the variable everyone adjusts last and should adjust first. The first quarter shows the intended effect; the second shows what the intended effect displaced. When we mapped it out, four of the seven steps existed only to compensate for the second one.

Documentation is a symptom: you write it where the design is unclear. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

What it is not

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

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 clearest signal was that people stopped asking where things were.

The expensive mistakes here are rarely the technical ones. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. In practice the answer showed up in the calendar before it showed up in the dashboard.

The vocabulary problem

The first thing to establish is what you are actually optimising for. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.

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