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.
Choosing what to measure
The tooling question is downstream of the constraint question. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
The expensive mistakes here are rarely the technical ones. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
The setup
Consistency is worth more than any individual improvement to politics. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. 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. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. That said, none of this generalises cleanly across team sizes.
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.
Where teams go wrong
Most of the difficulty lives at the boundaries, not in the middle. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
Feedback loops shorter than the planning cycle change everything. The first quarter shows the intended effect; the second shows what the intended effect displaced. When we mapped it out, four of the seven steps existed only to compensate for the second one.
Handing it over
The compounding effects matter far more than the individual wins. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. In practice the answer showed up in the calendar before it showed up in the dashboard.
What looks like a process problem is frequently an ownership problem. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.
Scope is the variable everyone adjusts last and should adjust first. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
When to change course
There is a version of politics that is mostly ritual. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. There are organisations where the opposite is true, and they are not obviously worse off.
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.
The default answer is right often enough to be dangerous. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
Start with the constraints
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. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
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. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
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.
The bottleneck is never where you think it is — that is what makes it a bottleneck.
— Overheard in a retrospective
A few things worth checking before you commit:
- Prefer the reversible option when the evidence is thin
- Decide in advance what would make you stop
- Name one person accountable — not a group
- Keep the feedback loop shorter than the planning cycle
- Write the constraint down before choosing a tool
Making it stick
Measurement is usually where this falls apart. 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.
The first thing to establish is what you are actually optimising for. Politics 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.
A worked example
The second-order effects arrive about a quarter after the first-order ones. 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. A useful test: if this disappeared tomorrow, how long before anyone noticed?
Nobody gets credit for the work that did not need doing. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. Set a date at which you will stop, and write down in advance what would make you stop earlier.
The first month
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 clearest signal was that people stopped asking where things were.
Consistency is worth more than any individual improvement to politics. 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.
Choosing what to measure
The compounding effects matter far more than the individual wins. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. This is easier to write than to hold to when a deadline appears.
The first thing to establish is what you are actually optimising for. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.
The second-order effects arrive about a quarter after the first-order ones. 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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
The setup
Feedback loops shorter than the planning cycle change everything. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. It is worth saying that we have not run this long enough to be confident.
There is a version of politics that is mostly ritual. 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.
Where teams go wrong
The interesting constraint is almost never the one in the brief. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. It is worth saying that we have not run this long enough to be confident.
The expensive mistakes here are rarely the technical ones. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.
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 evidence here is thinner than anyone quoting it tends to admit.
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.
