We spent a quarter trying to get design right, and the useful lessons were not the ones we expected.
A more modest claim
Speed and reversibility are the trade-off worth naming out loud. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. 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. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.
A different reading
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.
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. It is worth saying that we have not run this long enough to be confident.
The objection worth taking seriously
It helps to separate the decision from the execution. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
What looks like a process problem is frequently an ownership problem. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. The clearest signal was that people stopped asking where things were.
The received wisdom
The interesting constraint is almost never the one in the brief. 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.
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.
The incentive problem
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. This is easier to write than to hold to when a deadline appears.
The tooling question is downstream of the constraint question. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.
What the data actually shows
Documentation is a symptom: you write it where the design is unclear. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The evidence here is thinner than anyone quoting it tends to admit.
There is a version of design 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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
Consider the failure mode rather than the success case. 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 look for now:
- Agree on what "done" means, in writing, before starting
- Keep the feedback loop shorter than the planning cycle
- Write the constraint down before choosing a tool
- Review the numbers monthly; change the targets rarely
Where this leaves us
A shared definition of "done" removes more friction than any tool. The first quarter shows the intended effect; the second shows what the intended effect displaced. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
The default answer is right often enough to be dangerous. 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.
Most of the difficulty lives at the boundaries, not in the middle. Design rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. There are organisations where the opposite is true, and they are not obviously worse off.
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
What would change our mind
Consistency is worth more than any individual improvement to design. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. That said, none of this generalises cleanly across team sizes.
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. A useful test: if this disappeared tomorrow, how long before anyone noticed?
Feedback loops shorter than the planning cycle change everything. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
How we got here
The expensive mistakes here are rarely the technical ones. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
The second-order effects arrive about a quarter after the first-order ones. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. It is worth saying that we have not run this long enough to be confident.
A shared definition of "done" removes more friction than any tool. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. When we mapped it out, four of the seven steps existed only to compensate for the second one.
A more modest claim
The compounding effects matter far more than the individual wins. 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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
None of this generalises perfectly. Take the parts that map onto your constraints and discard the rest — that is what the framing is for.