Privacy Policy

There is no shortage of advice about independent editorial culture. There is a shortage of advice that survives contact with a real week.

When to change course

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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.

The second-order effects arrive about a quarter after the first-order ones. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

The first month

The compounding effects matter far more than the individual wins. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. The evidence here is thinner than anyone quoting it tends to admit.

The first thing to establish is what you are actually optimising for. The first quarter shows the intended effect; the second shows what the intended effect displaced.

A worked example

Nobody gets credit for the work that did not need doing. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. It is worth saying that we have not run this long enough to be confident.

A shared definition of "done" removes more friction than any tool. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

The bottleneck is never where you think it is — that is what makes it a bottleneck.

— Overheard in a retrospective

Start with the constraints

Documentation is a symptom: you write it where the design is unclear. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. When we mapped it out, four of the seven steps existed only to compensate for the second one.

It helps to separate the decision from the execution. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.

The checklist we ended up with:

1. Write the constraint down before choosing a tool
2. Agree on what "done" means, in writing, before starting
3. Keep the feedback loop shorter than the planning cycle
4. Name one person accountable — not a group
5. Review the numbers monthly; change the targets rarely

Choosing what to measure

Consistency is worth more than any individual improvement to independent editorial culture. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. The clearest signal was that people stopped asking where things were.

What looks like a process problem is frequently an ownership problem. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. A useful test: if this disappeared tomorrow, how long before anyone noticed?

None of this generalises perfectly. Take the parts that map onto your constraints and discard the rest — that is what the framing is for.