Getting started with slow living, properly

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

How it works

The expensive mistakes here are rarely the technical ones. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

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. Set a date at which you will stop, and write down in advance what would make you stop earlier.

The edge cases

Nobody gets credit for the work that did not need doing. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

Measurement is usually where this falls apart. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. It is worth saying that we have not run this long enough to be confident.

Consider the failure mode rather than the success case. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. When we mapped it out, four of the seven steps existed only to compensate for the second one.

A common misreading

The second-order effects arrive about a quarter after the first-order ones. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

There is a version of slow living that is mostly ritual. 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.

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. The version of this that works fits on an index card. The version that fails needs an onboarding session.

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 checklist we ended up with:

• Prefer the reversible option when the evidence is thin
• Name one person accountable — not a group
• Keep the feedback loop shorter than the planning cycle
• Review the numbers monthly; change the targets rarely
• Write the constraint down before choosing a tool

Why it is confusing

The interesting constraint is almost never the one in the brief. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. 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 slow living. Slow living rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

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.

What it is not

The default answer is right often enough to be dangerous. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. In practice the answer showed up in the calendar before it showed up in the dashboard.

A shared definition of "done" removes more friction than any tool. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The evidence here is thinner than anyone quoting it tends to admit.

Where to go deeper

What looks like a process problem is frequently an ownership problem. 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.

Speed and reversibility are the trade-off worth naming out loud. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.

Most of the difficulty lives at the boundaries, not in the middle. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The clearest signal was that people stopped asking where things were.

The vocabulary problem

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