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
The second-order effects arrive about a quarter after the first-order ones. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
Consistency is worth more than any individual improvement to general-interest daily news. 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. The clearest signal was that people stopped asking where things were.
Speed and reversibility are the trade-off worth naming out loud. The first quarter shows the intended effect; the second shows what the intended effect displaced.
The incentive problem
Documentation is a symptom: you write it where the design is unclear. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
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.
How we got here
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.
The tooling question is downstream of the constraint question. 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.
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. A useful test: if this disappeared tomorrow, how long before anyone noticed?
A more modest claim
The first thing to establish is what you are actually optimising for. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
Measurement is usually where this falls apart. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. That said, none of this generalises cleanly across team sizes.
A different reading
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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
You can have it fast, or you can have it reversible. Pick before you start, not after.
— Overheard in a retrospective
Where this leaves 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. Set a date at which you will stop, and write down in advance what would make you stop earlier.
Scope is the variable everyone adjusts last and should adjust first. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. When we mapped it out, four of the seven steps existed only to compensate for the second one.
What the data actually shows
Nobody gets credit for the work that did not need doing. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
There is a version of general-interest daily news that is mostly ritual. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. 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. 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.
What would change our mind
It helps to separate the decision from the execution. General-interest daily news rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
What looks like a process problem is frequently an ownership problem. 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 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.
What we look for now:
- Prefer the reversible option when the evidence is thin
- Keep the feedback loop shorter than the planning cycle
- Write the constraint down before choosing a tool
- Decide in advance what would make you stop
The objection worth taking seriously
Consider the failure mode rather than the success case. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
Most of the difficulty lives at the boundaries, not in the middle. 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.
The received wisdom
Measurement is usually where this falls apart. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
Feedback loops shorter than the planning cycle change everything. General-interest daily news rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. There are organisations where the opposite is true, and they are not obviously worse off.
The incentive problem
The interesting constraint is almost never the one in the brief. 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.
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. The evidence here is thinner than anyone quoting it tends to admit.
How we got here
Speed and reversibility are the trade-off worth naming out loud. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
There is a version of general-interest daily news that is mostly ritual. 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.
A more modest claim
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.
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.
The short version: decide what you are optimising for, write it down, and revisit it when the answer stops feeling obvious.
