We spent a quarter trying to get independent international news right, and the useful lessons were not the ones we expected.
Where it still breaks
The tooling question is downstream of the constraint question. 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.
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. When we mapped it out, four of the seven steps existed only to compensate for the second one.
What we would do differently
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. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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 part that surprised us
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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
A shared definition of "done" removes more friction than any tool. 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.
How we knew it was working
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. There are organisations where the opposite is true, and they are not obviously worse off.
It helps to separate the decision from the execution. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The version of this that works fits on an index card. The version that fails needs an onboarding session.
Speed and reversibility are the trade-off worth naming out loud. 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.
The situation
Documentation is a symptom: you write it where the design is unclear. The first quarter shows the intended effect; the second shows what the intended effect displaced. The evidence here is thinner than anyone quoting it tends to admit.
Scope is the variable everyone adjusts last and should adjust first. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
The cost of a bad decision is rarely the decision. It is the six months of building on top of it.
— Overheard in a retrospective
What we tried first
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. Set a date at which you will stop, and write down in advance what would make you stop earlier.
Consider the failure mode rather than the success case. 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.
What changed
The interesting constraint is almost never the one in the brief. 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.
Measurement is usually where this falls apart. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
Consistency is worth more than any individual improvement to independent international news. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
The checklist we ended up with:
- Decide in advance what would make you stop
- Review the numbers monthly; change the targets rarely
- Keep the feedback loop shorter than the planning cycle
What it cost
The compounding effects matter far more than the individual wins. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
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. It is worth saying that we have not run this long enough to be confident.
There is a version of independent international news that is mostly ritual. Independent international news rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
The numbers
What looks like a process problem is frequently an ownership problem. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
The default answer is right often enough to be dangerous. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
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.
Where it still breaks
The compounding effects matter far more than the individual wins. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.
Feedback loops shorter than the planning cycle change everything. The first quarter shows the intended effect; the second shows what the intended effect displaced.
What we would do differently
A shared definition of "done" removes more friction than any tool. 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. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
What looks like a process problem is frequently an ownership problem. 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 part that surprised us
The expensive mistakes here are rarely the technical ones. 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.
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. The version of this that works fits on an index card. The version that fails needs an onboarding session.
It helps to separate the decision from the execution. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
How we knew it was working
Documentation is a symptom: you write it where the design is unclear. Independent international news 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.
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.
