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.
Start with the constraints
Documentation is a symptom: you write it where the design is unclear. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. A useful test: if this disappeared tomorrow, how long before anyone noticed?
Most of the difficulty lives at the boundaries, not in the middle. 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
There is a version of business that is mostly ritual. 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.
Nobody gets credit for the work that did not need doing. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
Handing it over
The second-order effects arrive about a quarter after the first-order ones. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The clearest signal was that people stopped asking where things were.
The interesting constraint is almost never the one in the brief. Business rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
Consider the failure mode rather than the success case. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
Where teams go wrong
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 expensive mistakes here are rarely the technical ones. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
When to change course
Consistency is worth more than any individual improvement to business. 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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
A shared definition of "done" removes more friction than any tool. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
Every process is perfectly designed to get the results it gets.
— Overheard in a retrospective
Choosing what to measure
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.
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. That said, none of this generalises cleanly across team sizes.
Making it stick
The first thing to establish is what you are actually optimising for. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. This is easier to write than to hold to when a deadline appears.
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.
Scope is the variable everyone adjusts last and should adjust first. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.
The first month
It helps to separate the decision from the execution. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. The version of this that works fits on an index card. The version that fails needs an onboarding session.
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. There are organisations where the opposite is true, and they are not obviously worse off.
The setup
The tooling question is downstream of the constraint question. The first quarter shows the intended effect; the second shows what the intended effect displaced.
Speed and reversibility are the trade-off worth naming out loud. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.
Start with the constraints
The default answer is right often enough to be dangerous. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. When we mapped it out, four of the seven steps existed only to compensate for the second one.
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. It is worth saying that we have not run this long enough to be confident.
Documentation is a symptom: you write it where the design is unclear. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. In practice the answer showed up in the calendar before it showed up in the dashboard.
A worked example
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. When we mapped it out, four of the seven steps existed only to compensate for the second one.
A shared definition of "done" removes more friction than any tool. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
Handing it over
Most of the difficulty lives at the boundaries, not in the middle. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. Set a date at which you will stop, and write down in advance what would make you stop earlier.
The expensive mistakes here are rarely the technical ones. The first quarter shows the intended effect; the second shows what the intended effect displaced.
Scope is the variable everyone adjusts last and should adjust first. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. In practice the answer showed up in the calendar before it showed up in the dashboard.
What we look for now:
- Keep the feedback loop shorter than the planning cycle
- Decide in advance what would make you stop
- Write the constraint down before choosing a tool
- Name one person accountable — not a group
- Review the numbers monthly; change the targets rarely
Where teams go wrong
Nobody gets credit for the work that did not need doing. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.
It helps to separate the decision from the execution. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
The interesting constraint is almost never the one in the brief. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
None of this generalises perfectly. Take the parts that map onto your constraints and discard the rest — that is what the framing is for.
