About
Independent editorial culture is one of those topics where the obvious answer is right about sixty per cent of the time, which is exactly often enough to be dangerous.
The expensive mistake
Most of the difficulty lives at the boundaries, not in the middle. Independent editorial culture rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. The clearest signal was that people stopped asking where things were.
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 caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
The habit that compounds
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. In practice the answer showed up in the calendar before it showed up in the dashboard.
Measurement is usually where this falls apart. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. That said, none of this generalises cleanly across team sizes.
It helps to separate the decision from the execution. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
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 one that only matters at scale
The default answer is right often enough to be dangerous. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
Consider the failure mode rather than the success case. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
Speed and reversibility are the trade-off worth naming out loud. 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.
A few things worth checking before you commit:
- Decide in advance what would make you stop
- Write the constraint down before choosing a tool
- Keep the feedback loop shorter than the planning cycle
The one people skip
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. A useful test: if this disappeared tomorrow, how long before anyone noticed?
The expensive mistakes here are rarely the technical ones. The first quarter shows the intended effect; the second shows what the intended effect displaced. When we mapped it out, four of the seven steps existed only to compensate for the second one.
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.