There is no shortage of advice about competitive sport. There is a shortage of advice that survives contact with a real week.
The quiet win
Most of the difficulty lives at the boundaries, not in the middle. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
There is a version of competitive sport that is mostly ritual. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
The one that only matters at scale
Speed and reversibility are the trade-off worth naming out loud. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. The evidence here is thinner than anyone quoting it tends to admit.
Consistency is worth more than any individual improvement to competitive sport. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
Documentation is a symptom: you write it where the design is unclear. 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.
The one people skip
Measurement is usually where this falls apart. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.
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.
Feedback loops shorter than the planning cycle change everything. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. In practice the answer showed up in the calendar before it showed up in the dashboard.
Where to start on Monday
It helps to separate the decision from the execution. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. This is easier to write than to hold to when a deadline appears.
Scope is the variable everyone adjusts last and should adjust first. The first quarter shows the intended effect; the second shows what the intended effect displaced.
The second-order effects arrive about a quarter after the first-order ones. 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.
The advice worth ignoring
The expensive mistakes here are rarely the technical ones. Competitive sport rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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.
Nobody gets credit for the work that did not need doing. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
The habit that compounds
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.
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. It is worth saying that we have not run this long enough to be confident.
The tooling question is downstream of the constraint question. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next.
Simplicity is not the absence of work. It is the result of it.
— Overheard in a retrospective
What we look for now:
- Write the constraint down before choosing a tool
- Decide in advance what would make you stop
- Prefer the reversible option when the evidence is thin
- Review the numbers monthly; change the targets rarely
The expensive mistake
The compounding effects matter far more than the individual wins. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. Set a date at which you will stop, and write down in advance what would make you stop earlier.
A shared definition of "done" removes more friction than any tool. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.
What to do first
Consider the failure mode rather than the success case. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
The tooling question is downstream of the constraint question. 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.
Begin with the obvious one
A shared definition of "done" removes more friction than any tool. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
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. There are organisations where the opposite is true, and they are not obviously worse off.
The quiet win
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. The clearest signal was that people stopped asking where things were.
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 one that only matters at scale
The compounding effects matter far more than the individual wins. Competitive sport 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. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. That said, none of this generalises cleanly across team sizes.
The one people skip
The first thing to establish is what you are actually optimising for. 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.
There is a version of competitive sport that is mostly ritual. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. When we mapped it out, four of the seven steps existed only to compensate for the second one.
Where to start on Monday
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. 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. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. Set a date at which you will stop, and write down in advance what would make you stop earlier.
If there is one thing worth carrying away, it is that the expensive mistakes in competitive sport are almost never technical ones.
