We spent a quarter trying to get design right, and the useful lessons were not the ones we expected.
Where it still breaks
Measurement is usually where this falls apart. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
It helps to separate the decision from the execution. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
What looks like a process problem is frequently an ownership problem. 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 part that surprised us
Consider the failure mode rather than the success case. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The evidence here is thinner than anyone quoting it tends to admit.
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 situation
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. The version of this that works fits on an index card. The version that fails needs an onboarding session.
The expensive mistakes here are rarely the technical ones. 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.
Scope is the variable everyone adjusts last and should adjust first. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. This is easier to write than to hold to when a deadline appears.
What we would do differently
Documentation is a symptom: you write it where the design is unclear. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.
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. That said, none of this generalises cleanly across team sizes.
The bottleneck is never where you think it is — that is what makes it a bottleneck.
— Overheard in a retrospective
The numbers
A shared definition of "done" removes more friction than any tool. 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. There are organisations where the opposite is true, and they are not obviously worse off.
The tooling question is downstream of the constraint question. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.
What we tried first
The first thing to establish is what you are actually optimising for. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
Feedback loops shorter than the planning cycle change everything. The first quarter shows the intended effect; the second shows what the intended effect displaced. It is worth saying that we have not run this long enough to be confident.
The checklist we ended up with:
- Name one person accountable — not a group
- Agree on what "done" means, in writing, before starting
- Keep the feedback loop shorter than the planning cycle
What changed
Speed and reversibility are the trade-off worth naming out loud. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.
The default answer is right often enough to be dangerous. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
How we knew it was working
Most of the difficulty lives at the boundaries, not in the middle. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. The clearest signal was that people stopped asking where things were.
The compounding effects matter far more than the individual wins. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. This is easier to write than to hold to when a deadline appears.
Consistency is worth more than any individual improvement to design. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. In practice the answer showed up in the calendar before it showed up in the dashboard.
What it cost
There is a version of design that is mostly ritual. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. Set a date at which you will stop, and write down in advance what would make you stop earlier.
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. The evidence here is thinner than anyone quoting it tends to admit.
Most of the difficulty lives at the boundaries, not in the middle. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.
Where it still breaks
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.
Consider the failure mode rather than the success case. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. That said, none of this generalises cleanly across team sizes.
If there is one thing worth carrying away, it is that the expensive mistakes in design are almost never technical ones.