6 small changes that improve slow living

We spent a quarter trying to get slow living right, and the useful lessons were not the ones we expected.

What it cost

Consider the failure mode rather than the success case. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

The second-order effects arrive about a quarter after the first-order ones. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.

The first thing to establish is what you are actually optimising for. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. In practice the answer showed up in the calendar before it showed up in the dashboard.

What we would do differently

Measurement is usually where this falls apart. The first quarter shows the intended effect; the second shows what the intended effect displaced. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

The compounding effects matter far more than the individual wins. 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.

The numbers

There is a version of slow living that is mostly ritual. Slow living rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. When we mapped it out, four of the seven steps existed only to compensate for the second one.

The interesting constraint is almost never the one in the brief. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.

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

— Overheard in a retrospective

Where it still breaks

Consistency is worth more than any individual improvement to slow living. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

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.

What we tried first

Feedback loops shorter than the planning cycle change everything. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. A useful test: if this disappeared tomorrow, how long before anyone noticed?

The expensive mistakes here are rarely the technical ones. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.

What we look for now:

• Name one person accountable — not a group
• Agree on what "done" means, in writing, before starting
• Decide in advance what would make you stop
• Review the numbers monthly; change the targets rarely

The part that surprised us

A shared definition of "done" removes more friction than any tool. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. The clearest signal was that people stopped asking where things were.

Most of the difficulty lives at the boundaries, not in the middle. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. Set a date at which you will stop, and write down in advance what would make you stop earlier.

What changed

Scope is the variable everyone adjusts last and should adjust first. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. That said, none of this generalises cleanly across team sizes.

Speed and reversibility are the trade-off worth naming out loud. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.

How we knew it was working

Nobody gets credit for the work that did not need doing. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. The version of this that works fits on an index card. The version that fails needs an onboarding session.

It helps to separate the decision from the execution. 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.

If there is one thing worth carrying away, it is that the expensive mistakes in slow living are almost never technical ones.