Independent international news 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.
The incentive problem
Feedback loops shorter than the planning cycle change everything. 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.
The compounding effects matter far more than the individual wins. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
Consistency is worth more than any individual improvement to independent international news. 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.
A more modest claim
There is a version of independent international news that is mostly ritual. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
Documentation is a symptom: you write it where the design is unclear. 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.
A different reading
Nobody gets credit for the work that did not need doing. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.
Measurement is usually where this falls apart. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
The default answer is right often enough to be dangerous. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.
The objection worth taking seriously
The second-order effects arrive about a quarter after the first-order ones. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. In practice the answer showed up in the calendar before it showed up in the dashboard.
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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
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.
Every process is perfectly designed to get the results it gets.
— Overheard in a retrospective
How we got here
Speed and reversibility are the trade-off worth naming out loud. 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?
Consider the failure mode rather than the success case. 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.
What would change our mind
The interesting constraint is almost never the one in the brief. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. The clearest signal was that people stopped asking where things were.
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.
What the data actually shows
The first thing to establish is what you are actually optimising for. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
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. 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. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
A few things worth checking before you commit:
- Keep the feedback loop shorter than the planning cycle
- Agree on what "done" means, in writing, before starting
- Name one person accountable — not a group
The received wisdom
A shared definition of "done" removes more friction than any tool. Independent international news rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
Most of the difficulty lives at the boundaries, not in the middle. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.
Where this leaves us
Nobody gets credit for the work that did not need doing. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. 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 independent international news. 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.
A shared definition of "done" removes more friction than any tool. 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. That said, none of this generalises cleanly across team sizes.
The incentive problem
The interesting constraint is almost never the one in the brief. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.
The tooling question is downstream of the constraint question. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
A more modest claim
It helps to separate the decision from the execution. 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.
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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
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.
A different reading
The second-order effects arrive about a quarter after the first-order ones. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. The version of this that works fits on an index card. The version that fails needs an onboarding session.
Documentation is a symptom: you write it where the design is unclear. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. Set a date at which you will stop, and write down in advance what would make you stop earlier.
The objection worth taking seriously
The first thing to establish is what you are actually optimising for. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The clearest signal was that people stopped asking where things were.
None of this generalises perfectly. Take the parts that map onto your constraints and discard the rest — that is what the framing is for.
