The interesting thing about strength training is how rarely the hard part is the part everyone prepares for.
Handing it over
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. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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. 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. 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.
Choosing what to measure
The tooling question is downstream of the constraint question. Strength training rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
Consistency is worth more than any individual improvement to strength training. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. There are organisations where the opposite is true, and they are not obviously worse off.
The setup
Measurement is usually where this falls apart. 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. 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. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.
When to change course
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. 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. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. The clearest signal was that people stopped asking where things were.
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. When we mapped it out, four of the seven steps existed only to compensate for the second one.
Simplicity is not the absence of work. It is the result of it.
— Overheard in a retrospective
Start with the constraints
Scope is the variable everyone adjusts last and should adjust first. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. In practice the answer showed up in the calendar before it showed up in the dashboard.
Speed and reversibility are the trade-off worth naming out loud. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
Where teams go wrong
There is a version of strength training that is mostly ritual. 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. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. 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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
A worked example
Consider the failure mode rather than the success case. 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.
The first thing to establish is what you are actually optimising for. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. This is easier to write than to hold to when a deadline appears.
What we look for now:
- Review the numbers monthly; change the targets rarely
- Name one person accountable — not a group
- Decide in advance what would make you stop
- Prefer the reversible option when the evidence is thin
- Keep the feedback loop shorter than the planning cycle
The first month
It helps to separate the decision from the execution. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. 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. 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.
Making it stick
Documentation is a symptom: you write it where the design is unclear. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. 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 strength training. 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.
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 evidence here is thinner than anyone quoting it tends to admit.
Handing it over
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. The clearest signal was that people stopped asking where things were.
What looks like a process problem is frequently an ownership problem. 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.
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. This is easier to write than to hold to when a deadline appears.
Choosing what to measure
The interesting constraint is almost never the one in the brief. The first quarter shows the intended effect; the second shows what the intended effect displaced.
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. 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. 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.
The short version: decide what you are optimising for, write it down, and revisit it when the answer stops feeling obvious.
