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.
The setup
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 expensive mistakes here are rarely the technical ones. The first quarter shows the intended effect; the second shows what the intended effect displaced.
A worked example
There is a version of business that is mostly ritual. 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. It is worth saying that we have not run this long enough to be confident.
Nobody gets credit for the work that did not need doing. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
Most of the difficulty lives at the boundaries, not in the middle. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. The evidence here is thinner than anyone quoting it tends to admit.
Start with the constraints
Consistency is worth more than any individual improvement to business. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. When we mapped it out, four of the seven steps existed only to compensate for the second one.
The default answer is right often enough to be dangerous. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The clearest signal was that people stopped asking where things were.
Where teams go wrong
The tooling question is downstream of the constraint question. Business rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
Documentation is a symptom: you write it where the design is unclear. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. 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. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. A useful test: if this disappeared tomorrow, how long before anyone noticed?
The first month
The compounding effects matter far more than the individual wins. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.
Feedback loops shorter than the planning cycle change everything. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
Scope is the variable everyone adjusts last and should adjust first. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
You can have it fast, or you can have it reversible. Pick before you start, not after.
— Overheard in a retrospective
Making it stick
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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
It helps to separate the decision from the execution. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
Handing it over
What looks like a process problem is frequently an ownership problem. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
A shared definition of "done" removes more friction than any tool. 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 first thing to establish is what you are actually optimising for. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.
Choosing what to measure
Measurement is usually where this falls apart. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.
The interesting constraint is almost never the one in the brief. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. Set a date at which you will stop, and write down in advance what would make you stop earlier.
Scope is the variable everyone adjusts last and should adjust first. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. In practice the answer showed up in the calendar before it showed up in the dashboard.
A few things worth checking before you commit:
- Name one person accountable — not a group
- Agree on what "done" means, in writing, before starting
- Decide in advance what would make you stop
- Prefer the reversible option when the evidence is thin
When to change course
Nobody gets credit for the work that did not need doing. Business rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
What looks like a process problem is frequently an ownership problem. 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. The first quarter shows the intended effect; the second shows what the intended effect displaced. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
The setup
The tooling question is downstream of the constraint question. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. When we mapped it out, four of the seven steps existed only to compensate for the second one.
Measurement is usually where this falls apart. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.
A worked example
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.
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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
Start with the constraints
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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
Documentation is a symptom: you write it where the design is unclear. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. In practice the answer showed up in the calendar before it showed up in the dashboard.
Where teams go wrong
Most of the difficulty lives at the boundaries, not in the middle. 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. This is easier to write than to hold to when a deadline appears.
The expensive mistakes here are rarely the technical ones. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.
If there is one thing worth carrying away, it is that the expensive mistakes in business are almost never technical ones.
