We spent a quarter trying to get general-interest daily news right, and the useful lessons were not the ones we expected.
The part that surprised us
Most of the difficulty lives at the boundaries, not in the middle. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. That said, none of this generalises cleanly across team sizes.
The second-order effects arrive about a quarter after the first-order ones. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
A shared definition of "done" removes more friction than any tool. 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.
How we knew it was working
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.
Consider the failure mode rather than the success case. General-interest daily news rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
Scope is the variable everyone adjusts last and should adjust first. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
Where it still breaks
The compounding effects matter far more than the individual wins. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. It is worth saying that we have not run this long enough to be confident.
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. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
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.
What changed
The first thing to establish is what you are actually optimising for. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. The clearest signal was that people stopped asking where things were.
The tooling question is downstream of the constraint question. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. Set a date at which you will stop, and write down in advance what would make you stop earlier.
What looks like a process problem is frequently an ownership problem. 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.
What we tried first
Consistency is worth more than any individual improvement to general-interest daily news. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. The version of this that works fits on an index card. The version that fails needs an onboarding session.
The interesting constraint is almost never the one in the brief. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.
What it cost
Nobody gets credit for the work that did not need doing. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
Documentation is a symptom: you write it where the design is unclear. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. There are organisations where the opposite is true, and they are not obviously worse off.
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.
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
The checklist we ended up with:
- Decide in advance what would make you stop
- Name one person accountable — not a group
- Review the numbers monthly; change the targets rarely
What we would do differently
There is a version of general-interest daily news that is mostly ritual. The first quarter shows the intended effect; the second shows what the intended effect displaced.
The expensive mistakes here are rarely the technical ones. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
The numbers
The default answer is right often enough to be dangerous. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.
Measurement is usually where this falls apart. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. This is easier to write than to hold to when a deadline appears.
The situation
Consistency is worth more than any individual improvement to general-interest daily news. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
Feedback loops shorter than the planning cycle change everything. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
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. That said, none of this generalises cleanly across team sizes.
The part that surprised us
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. In practice the answer showed up in the calendar before it showed up in the dashboard.
It helps to separate the decision from the execution. The first quarter shows the intended effect; the second shows what the intended effect displaced. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
The tooling question is downstream of the constraint question. 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.
How we knew it was working
Most of the difficulty lives at the boundaries, not in the middle. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. The evidence here is thinner than anyone quoting it tends to admit.
What looks like a process problem is frequently an ownership problem. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
Where it still breaks
The interesting constraint is almost never the one in the brief. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. 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. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.
What changed
Nobody gets credit for the work that did not need doing. General-interest daily news rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. This is easier to write than to hold to when a deadline appears.
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.
