We spent a quarter trying to get general-interest daily news right, and the useful lessons were not the ones we expected.
A more modest claim
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. The version of this that works fits on an index card. The version that fails needs an onboarding session.
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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
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. It is worth saying that we have not run this long enough to be confident.
The received wisdom
Speed and reversibility are the trade-off worth naming out loud. 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. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.
How we got here
There is a version of general-interest daily news that is mostly ritual. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.
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. When we mapped it out, four of the seven steps existed only to compensate for the second one.
The incentive problem
The expensive mistakes here are rarely the technical ones. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.
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. Set a date at which you will stop, and write down in advance what would make you stop earlier.
The default answer is right often enough to be dangerous. 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?
The objection worth taking seriously
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. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
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. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
Simplicity is not the absence of work. It is the result of it.
— Overheard in a retrospective
A different reading
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 first thing to establish is what you are actually optimising for. 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.
Where this leaves us
Nobody gets credit for the work that did not need doing. The first quarter shows the intended effect; the second shows what the intended effect displaced.
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. In practice the answer showed up in the calendar before it showed up in the dashboard.
What the data actually shows
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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
Consistency is worth more than any individual improvement to general-interest daily news. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
It helps to separate the decision from the execution. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. The clearest signal was that people stopped asking where things were.
A few things worth checking before you commit:
- Write the constraint down before choosing a tool
- Review the numbers monthly; change the targets rarely
- Name one person accountable — not a group
- Decide in advance what would make you stop
- Agree on what "done" means, in writing, before starting
What would change our mind
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.
Feedback loops shorter than the planning cycle change everything. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. This is easier to write than to hold to when a deadline appears.
A more modest claim
Most of the difficulty lives at the boundaries, not in the middle. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
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.
The received wisdom
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 expensive mistakes here are rarely the technical ones. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.
How we got here
Consistency is worth more than any individual improvement to general-interest daily news. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
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. That said, none of this generalises cleanly across team sizes.
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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
The incentive problem
The default answer is right often enough to be dangerous. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
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. 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. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. The evidence here is thinner than anyone quoting it tends to admit.
None of this generalises perfectly. Take the parts that map onto your constraints and discard the rest — that is what the framing is for.
