We spent a quarter trying to get general-interest daily news right, and the useful lessons were not the ones we expected.
Where it still breaks
Scope is the variable everyone adjusts last and should adjust first. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.
A shared definition of "done" removes more friction than any tool. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. In practice the answer showed up in the calendar before it showed up in the dashboard.
The situation
The second-order effects arrive about a quarter after the first-order ones. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. That said, none of this generalises cleanly across team sizes.
Feedback loops shorter than the planning cycle change everything. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.
Measurement is usually where this falls apart. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next.
What we tried first
Speed and reversibility are the trade-off worth naming out loud. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.
The default answer is right often enough to be dangerous. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. This is easier to write than to hold to when a deadline appears.
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. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
The numbers
The tooling question is downstream of the constraint question. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
The interesting constraint is almost never the one in the brief. 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 first thing to establish is what you are actually optimising for. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. There are organisations where the opposite is true, and they are not obviously worse off.
What it cost
What looks like a process problem is frequently an ownership problem. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.
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.
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.
You can have it fast, or you can have it reversible. Pick before you start, not after.
— Overheard in a retrospective
The part that surprised us
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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
Consider the failure mode rather than the success case. The first quarter shows the intended effect; the second shows what the intended effect displaced. The clearest signal was that people stopped asking where things were.
Documentation is a symptom: you write it where the design is unclear. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. 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
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.
Nobody gets credit for the work that did not need doing. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
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.
What we would do differently
Speed and reversibility are the trade-off worth naming out loud. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
The first thing to establish is what you are actually optimising for. 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 evidence here is thinner than anyone quoting it tends to admit.
What changed
Consider the failure mode rather than the success case. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
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. When we mapped it out, four of the seven steps existed only to compensate for the second one.
What we look for now:
- Keep the feedback loop shorter than the planning cycle
- Review the numbers monthly; change the targets rarely
- Name one person accountable — not a group
- Write the constraint down before choosing a tool
- Prefer the reversible option when the evidence is thin
Where it still breaks
What looks like a process problem is frequently an ownership problem. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.
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. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
The tooling question is downstream of the constraint question. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
The situation
The default answer is right often enough to be dangerous. General-interest daily news rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
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. Set a date at which you will stop, and write down in advance what would make you stop earlier.
What we tried first
A shared definition of "done" removes more friction than any tool. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
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 numbers
The compounding effects matter far more than the individual wins. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.
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.
Scope is the variable everyone adjusts last and should adjust first. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
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.
