Ask ten people to define business and you will get ten answers, most of them describing a symptom rather than the thing itself.
Where this leaves us
Speed and reversibility are the trade-off worth naming out loud. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
Nobody gets credit for the work that did not need doing. 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.
How we got here
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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
The second-order effects arrive about a quarter after the first-order ones. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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 evidence here is thinner than anyone quoting it tends to admit.
A different reading
What looks like a process problem is frequently an ownership problem. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. When we mapped it out, four of the seven steps existed only to compensate for the second one.
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. There are organisations where the opposite is true, and they are not obviously worse off.
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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
The incentive problem
A shared definition of "done" removes more friction than any tool. Business rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
Scope is the variable everyone adjusts last and should adjust first. 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.
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 clearest signal was that people stopped asking where things were.
The objection worth taking seriously
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. 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. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
What would change our mind
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 counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
The default answer is right often enough to be dangerous. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.
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. Set a date at which you will stop, and write down in advance what would make you stop earlier.
A few things worth checking before you commit:
- Keep the feedback loop shorter than the planning cycle
- Decide in advance what would make you stop
- Review the numbers monthly; change the targets rarely
- Agree on what "done" means, in writing, before starting
- Write the constraint down before choosing a tool
The received wisdom
There is a version of business that is mostly ritual. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.
Consider the failure mode rather than the success case. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.
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. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
Consistency is worth more than any individual improvement to business. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
A more modest claim
The interesting constraint is almost never the one in the brief. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.
The compounding effects matter far more than the individual wins. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. In practice the answer showed up in the calendar before it showed up in the dashboard.
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.
Where this leaves us
The expensive mistakes here are rarely the technical ones. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
Speed and reversibility are the trade-off worth naming out loud. Business rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
The first thing to establish is what you are actually optimising for. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. The version of this that works fits on an index card. The version that fails needs an onboarding session.
How we got here
What looks like a process problem is frequently an ownership problem. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. The version of this that works fits on an index card. The version that fails needs an onboarding session.
Consistency is worth more than any individual improvement to business. 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?
A different reading
The tooling question is downstream of the constraint question. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
The second-order effects arrive about a quarter after the first-order ones. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. This is easier to write than to hold to when a deadline appears.
Measurement is usually where this falls apart. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
If there is one thing worth carrying away, it is that the expensive mistakes in business are almost never technical ones.
