Ask ten people to define design and you will get ten answers, most of them describing a symptom rather than the thing itself.
Where it still breaks
Most of the difficulty lives at the boundaries, not in the middle. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
The interesting constraint is almost never the one in the brief. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. It is worth saying that we have not run this long enough to be confident.
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.
What we tried first
The first thing to establish is what you are actually optimising for. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.
Nobody gets credit for the work that did not need doing. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.
The situation
Scope is the variable everyone adjusts last and should adjust first. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
Documentation is a symptom: you write it where the design is unclear. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. The evidence here is thinner than anyone quoting it tends to admit.
Feedback loops shorter than the planning cycle change everything. 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 caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
What we would do differently
It helps to separate the decision from the execution. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.
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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
Consider the failure mode rather than the success case. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
Every process is perfectly designed to get the results it gets.
— Overheard in a retrospective
What changed
Speed and reversibility are the trade-off worth naming out loud. Design rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. Set a date at which you will stop, and write down in advance what would make you stop earlier.
The second-order effects arrive about a quarter after the first-order ones. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.
What looks like a process problem is frequently an ownership problem. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.
What it cost
Measurement is usually where this falls apart. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
The expensive mistakes here are rarely the technical ones. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. That said, none of this generalises cleanly across team sizes.
How we knew it was working
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.
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. When we mapped it out, four of the seven steps existed only to compensate for the second one.
There is a version of design that is mostly ritual. The first quarter shows the intended effect; the second shows what the intended effect displaced. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
What we look for now:
- 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
- Prefer the reversible option when the evidence is thin
The part that surprised us
A shared definition of "done" removes more friction than any tool. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
It helps to separate the decision from the execution. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. There are organisations where the opposite is true, and they are not obviously worse off.
The numbers
Nobody gets credit for the work that did not need doing. Design rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
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.
Where it still breaks
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. 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. 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.
Consistency is worth more than any individual improvement to design. 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.
None of this generalises perfectly. Take the parts that map onto your constraints and discard the rest — that is what the framing is for.