We spent a quarter trying to get general-interest daily news right, and the useful lessons were not the ones we expected.
The received wisdom
Consistency is worth more than any individual improvement to general-interest daily news. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
The first thing to establish is what you are actually optimising for. General-interest daily news rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. Set a date at which you will stop, and write down in advance what would make you stop earlier.
The expensive mistakes here are rarely the technical ones. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The clearest signal was that people stopped asking where things were.
The objection worth taking seriously
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. The evidence here is thinner than anyone quoting it tends to admit.
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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
What the data actually shows
Consider the failure mode rather than the success case. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. There are organisations where the opposite is true, and they are not obviously worse off.
Measurement is usually where this falls apart. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. A useful test: if this disappeared tomorrow, how long before anyone noticed?
The incentive problem
What looks like a process problem is frequently an ownership problem. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
Scope is the variable everyone adjusts last and should adjust first. 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.
What would change our mind
A shared definition of "done" removes more friction than any tool. 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 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. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
Every process is perfectly designed to get the results it gets.
— Overheard in a retrospective
Where this leaves us
The tooling question is downstream of the constraint question. The first quarter shows the intended effect; the second shows what the intended effect displaced.
Most of the difficulty lives at the boundaries, not in the middle. 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. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
A different reading
Nobody gets credit for the work that did not need doing. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.
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.
A few things worth checking before you commit:
- Keep the feedback loop shorter than the planning cycle
- Name one person accountable — not a group
- Decide in advance what would make you stop
How we got here
There is a version of general-interest daily news that is mostly ritual. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
The interesting constraint is almost never the one in the brief. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. In practice the answer showed up in the calendar before it showed up in the dashboard.
A more modest claim
The second-order effects arrive about a quarter after the first-order ones. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. This is easier to write than to hold to when a deadline appears.
Feedback loops shorter than the planning cycle change everything. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. When we mapped it out, four of the seven steps existed only to compensate for the second one.
Most of the difficulty lives at the boundaries, not in the middle. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.
The received wisdom
Scope is the variable everyone adjusts last and should adjust first. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
The compounding effects matter far more than the individual wins. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
There is a version of general-interest daily news that is mostly ritual. General-interest daily news rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
The objection worth taking seriously
What looks like a process problem is frequently an ownership problem. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.
The expensive mistakes here are rarely the technical ones. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
Documentation is a symptom: you write it where the design is unclear. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
What the data actually shows
Nobody gets credit for the work that did not need doing. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The version of this that works fits on an index card. The version that fails needs an onboarding session.
The tooling question is downstream of the constraint question. 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 incentive problem
It helps to separate the decision from the execution. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
Speed and reversibility are the trade-off worth naming out loud. 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?
If there is one thing worth carrying away, it is that the expensive mistakes in general-interest daily news are almost never technical ones.
