Business is one of those topics where the obvious answer is right about sixty per cent of the time, which is exactly often enough to be dangerous.
How we got here
It helps to separate the decision from the execution. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
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. In practice the answer showed up in the calendar before it showed up in the dashboard.
A different reading
There is a version of business that is mostly ritual. 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.
Speed and reversibility are the trade-off worth naming out loud. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. There are organisations where the opposite is true, and they are not obviously worse off.
The received wisdom
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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
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. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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. When we mapped it out, four of the seven steps existed only to compensate for the second one.
A more modest claim
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. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.
Where this leaves us
Consistency is worth more than any individual improvement to business. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. That said, none of this generalises cleanly across team sizes.
A shared definition of "done" removes more friction than any tool. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
The bottleneck is never where you think it is — that is what makes it a bottleneck.
— Overheard in a retrospective
What the data actually shows
Measurement is usually where this falls apart. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
Feedback loops shorter than the planning cycle change everything. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.
The incentive problem
Most of the difficulty lives at the boundaries, not in the middle. Business rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
The default answer is right often enough to be dangerous. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. This is easier to write than to hold to when a deadline appears.
The objection worth taking seriously
The first thing to establish is what you are actually optimising for. 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 version of this that works fits on an index card. The version that fails needs an onboarding session.
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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
What looks like a process problem is frequently an ownership problem. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. The clearest signal was that people stopped asking where things were.
A few things worth checking before you commit:
- Keep the feedback loop shorter than the planning cycle
- Prefer the reversible option when the evidence is thin
- Decide in advance what would make you stop
What would change our mind
The expensive mistakes here are rarely the technical ones. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.
Consider the failure mode rather than the success case. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
The tooling question is downstream of the constraint question. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. Set a date at which you will stop, and write down in advance what would make you stop earlier.
How we got here
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.
Measurement is usually where this falls apart. 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.
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.
A different reading
Consider the failure mode rather than the success case. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.
Documentation is a symptom: you write it where the design is unclear. 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.
The received wisdom
The expensive mistakes here are rarely the technical ones. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
There is a version of business 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.
A more modest claim
A shared definition of "done" removes more friction than any tool. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. The evidence here is thinner than anyone quoting it tends to admit.
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.
The compounding effects matter far more than the individual wins. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
We will revisit this once we have another two quarters of data. The current answer feels right, which is exactly when it is worth checking.
