Politics 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.
What would change our mind
What looks like a process problem is frequently an ownership problem. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. That said, none of this generalises cleanly across team sizes.
Feedback loops shorter than the planning cycle change everything. Politics rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
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.
The received wisdom
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. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
A shared definition of "done" removes more friction than any tool. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. 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 politics that is mostly ritual. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. The clearest signal was that people stopped asking where things were.
How we got here
Speed and reversibility are the trade-off worth naming out loud. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. 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. 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.
The objection worth taking seriously
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. In practice the answer showed up in the calendar before it showed up in the dashboard.
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.
Measurement is usually where this falls apart. 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.
The bottleneck is never where you think it is — that is what makes it a bottleneck.
— Overheard in a retrospective
Where this leaves us
Consistency is worth more than any individual improvement to politics. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.
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.
Most of the difficulty lives at the boundaries, not in the middle. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. There are organisations where the opposite is true, and they are not obviously worse off.
The incentive problem
The expensive mistakes here are rarely the technical ones. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.
The compounding effects matter far more than the individual wins. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
A more modest claim
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. 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. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
Consider the failure mode rather than the success case. The first quarter shows the intended effect; the second shows what the intended effect displaced. Set a date at which you will stop, and write down in advance what would make you stop earlier.
What we look for now:
- Name one person accountable — not a group
- Write the constraint down before choosing a tool
- Review the numbers monthly; change the targets rarely
- Prefer the reversible option when the evidence is thin
A different reading
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.
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.
What the data actually shows
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 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.
Consider the failure mode rather than the success case. The first quarter shows the intended effect; the second shows what the intended effect displaced.
What would change our mind
The expensive mistakes here are rarely the technical ones. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
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. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
The received wisdom
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. 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 compounding effects matter far more than the individual wins. 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.
How we got here
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 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 politics. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
It helps to separate the decision from the execution. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.
If there is one thing worth carrying away, it is that the expensive mistakes in politics are almost never technical ones.
