The interesting thing about design is how rarely the hard part is the part everyone prepares for.
A more modest claim
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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
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.
How we got here
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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
There is a version of design 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.
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. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
What would change our mind
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 version of this that works fits on an index card. The version that fails needs an onboarding session.
What looks like a process problem is frequently an ownership problem. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. The evidence here is thinner than anyone quoting it tends to admit.
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.
The objection worth taking seriously
The second-order effects arrive about a quarter after the first-order 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.
Consider the failure mode rather than the success case. Design rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
The received wisdom
The interesting constraint is almost never the one in the brief. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. In practice the answer showed up in the calendar before it showed up in the dashboard.
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. Set a date at which you will stop, and write down in advance what would make you stop earlier.
Most of the difficulty lives at the boundaries, not in the middle. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. That said, none of this generalises cleanly across team sizes.
A different reading
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.
The compounding effects matter far more than the individual wins. 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.
You can have it fast, or you can have it reversible. Pick before you start, not after.
— Overheard in a retrospective
Where this leaves us
Consistency is worth more than any individual improvement to design. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. The clearest signal was that people stopped asking where things were.
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.
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 incentive problem
Documentation is a symptom: you write it where the design is unclear. 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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
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. It is worth saying that we have not run this long enough to be confident.
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.
What the data actually shows
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. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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. When we mapped it out, four of the seven steps existed only to compensate for the second one.
A more modest claim
What looks like a process problem is frequently an ownership problem. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
The compounding effects matter far more than the individual wins. 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 interesting constraint is almost never the one in the brief. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. A useful test: if this disappeared tomorrow, how long before anyone noticed?
What we look for now:
- Review the numbers monthly; change the targets rarely
- Decide in advance what would make you stop
- Name one person accountable — not a group
- Keep the feedback loop shorter than the planning cycle
- Agree on what "done" means, in writing, before starting
None of this generalises perfectly. Take the parts that map onto your constraints and discard the rest — that is what the framing is for.