The interesting thing about design is how rarely the hard part is the part everyone prepares for.
Why it is confusing
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. That said, none of this generalises cleanly across team sizes.
There is a version of design that is mostly ritual. 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 evidence here is thinner than anyone quoting it tends to admit.
The short version
The default answer is right often enough to be dangerous. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
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 caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
The first thing to establish is what you are actually optimising for. 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.
A common misreading
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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
The compounding effects matter far more than the individual wins. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. It is worth saying that we have not run this long enough to be confident.
How it works
The interesting constraint is almost never the one in the brief. 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.
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.
The bottleneck is never where you think it is — that is what makes it a bottleneck.
— Overheard in a retrospective
Putting it together
What looks like a process problem is frequently an ownership problem. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
Most of the difficulty lives at the boundaries, not in the middle. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.
Consistency is worth more than any individual improvement to design. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.
What it is not
Consider the failure mode rather than the success case. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.
Speed and reversibility are the trade-off worth naming out loud. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
Scope is the variable everyone adjusts last and should adjust first. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. There are organisations where the opposite is true, and they are not obviously worse off.
Where to go deeper
Nobody gets credit for the work that did not need doing. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. 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. Design rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
The checklist we ended up with:
- Write the constraint down before choosing a tool
- Name one person accountable — not a group
- Agree on what "done" means, in writing, before starting
- Prefer the reversible option when the evidence is thin
The edge cases
Documentation is a symptom: you write it where the design is unclear. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
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 tooling question is downstream of the constraint question. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
The vocabulary problem
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.
Consider the failure mode rather than the success case. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.
Why it is confusing
It helps to separate the decision from the execution. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.
Consistency is worth more than any individual improvement to design. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. A useful test: if this disappeared tomorrow, how long before anyone noticed?
The short version
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.
The expensive mistakes here are rarely the technical ones. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. This is easier to write than to hold to when a deadline appears.
The short version: decide what you are optimising for, write it down, and revisit it when the answer stops feeling obvious.