We spent a quarter trying to get business right, and the useful lessons were not the ones we expected.
Where this leaves us
Feedback loops shorter than the planning cycle change everything. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
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. In practice the answer showed up in the calendar before it showed up in the dashboard.
A more modest claim
Consider the failure mode rather than the success case. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
What looks like a process problem is frequently an ownership problem. 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.
What the data actually shows
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.
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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
The incentive problem
There is a version of business 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.
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. This is easier to write than to hold to when a deadline appears.
What would change our mind
The compounding effects matter far more than the individual wins. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
Nobody gets credit for the work that did not need doing. 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.
The objection worth taking seriously
The tooling question is downstream of the constraint question. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
Measurement is usually where this falls apart. The first quarter shows the intended effect; the second shows what the intended effect displaced.
The received wisdom
Documentation is a symptom: you write it where the design is unclear. 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 evidence here is thinner than anyone quoting it tends to admit.
It helps to separate the decision from the execution. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. The clearest signal was that people stopped asking where things were.
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
How we got here
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.
The second-order effects arrive about a quarter after the first-order ones. 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.
A few things worth checking before you commit:
- Review the numbers monthly; change the targets rarely
- Decide in advance what would make you stop
- Keep the feedback loop shorter than the planning cycle
- Prefer the reversible option when the evidence is thin
- Agree on what "done" means, in writing, before starting
A different reading
The default answer is right often enough to be dangerous. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. It is worth saying that we have not run this long enough to be confident.
Consistency is worth more than any individual improvement to business. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
Where this leaves us
The expensive mistakes here are rarely the technical ones. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. 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. Business rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
A more modest claim
Consistency is worth more than any individual improvement to business. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. The version of this that works fits on an index card. The version that fails needs an onboarding session.
There is a version of business that is mostly ritual. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. It is worth saying that we have not run this long enough to be confident.
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. A useful test: if this disappeared tomorrow, how long before anyone noticed?
What the data actually shows
The interesting constraint is almost never the one in the brief. 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.
Nobody gets credit for the work that did not need doing. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
The incentive problem
The first thing to establish is what you are actually optimising for. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
Speed and reversibility are the trade-off worth naming out loud. The first quarter shows the intended effect; the second shows what the intended effect displaced. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
What would change our mind
A shared definition of "done" removes more friction than any tool. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. The evidence here is thinner than anyone quoting it tends to admit.
The second-order effects arrive about a quarter after the first-order ones. Business rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
If there is one thing worth carrying away, it is that the expensive mistakes in business are almost never technical ones.
