There is no shortage of advice about competitive sport. There is a shortage of advice that survives contact with a real week.
What changed
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. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
The compounding effects matter far more than the individual wins. The first quarter shows the intended effect; the second shows what the intended effect displaced. The clearest signal was that people stopped asking where things were.
What we tried first
The second-order effects arrive about a quarter after the first-order ones. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next.
Most of the difficulty lives at the boundaries, not in the middle. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. That said, none of this generalises cleanly across team sizes.
The default answer is right often enough to be dangerous. 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.
How we knew it was working
The interesting constraint is almost never the one in the brief. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
Scope is the variable everyone adjusts last and should adjust first. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
Documentation is a symptom: you write it where the design is unclear. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. Set a date at which you will stop, and write down in advance what would make you stop earlier.
Where it still breaks
Feedback loops shorter than the planning cycle change everything. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. The evidence here is thinner than anyone quoting it tends to admit.
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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
What we would do differently
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. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
The numbers
What looks like a process problem is frequently an ownership problem. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.
Speed and reversibility are the trade-off worth naming out loud. Competitive sport rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
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. In practice the answer showed up in the calendar before it showed up in the dashboard.
What it cost
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 version of this that works fits on an index card. The version that fails needs an onboarding session.
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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
Simplicity is not the absence of work. It is the result of it.
— Overheard in a retrospective
A few things worth checking before you commit:
- Write the constraint down before choosing a tool
- Decide in advance what would make you stop
- Name one person accountable — not a group
- Review the numbers monthly; change the targets rarely
The situation
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. 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. 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?
There is a version of competitive sport that is mostly ritual. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.
The part that surprised us
Consider the failure mode rather than the success case. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.
The first thing to establish is what you are actually optimising for. Competitive sport rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. The version of this that works fits on an index card. The version that fails needs an onboarding session.
What looks like a process problem is frequently an ownership problem. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
What changed
There is a version of competitive sport 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. There are organisations where the opposite is true, and they are not obviously worse off.
It helps to separate the decision from the execution. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. Set a date at which you will stop, and write down in advance what would make you stop earlier.
What we tried first
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. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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.
How we knew it was working
The tooling question is downstream of the constraint question. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.
Measurement is usually where this falls apart. The first quarter shows the intended effect; the second shows what the intended effect displaced. This is easier to write than to hold to when a deadline appears.
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.
Where it still breaks
The compounding effects matter far more than the individual wins. 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.
We will revisit this once we have another two quarters of data. The current answer feels right, which is exactly when it is worth checking.
