A practical guide to slow living

Ask ten people to define slow living and you will get ten answers, most of them describing a symptom rather than the thing itself.

Handing it over

Speed and reversibility are the trade-off worth naming out loud. Slow living 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.

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.

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

Where teams go wrong

Measurement is usually where this falls apart. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.

The second-order effects arrive about a quarter after the first-order 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.

Most of the difficulty lives at the boundaries, not in the middle. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next.

A worked example

Scope is the variable everyone adjusts last and should adjust first. 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.

The interesting constraint is almost never the one in the brief. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.

The expensive mistakes here are rarely the technical ones. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.

You can have it fast, or you can have it reversible. Pick before you start, not after.

— Overheard in a retrospective

Start with the constraints

A shared definition of "done" removes more friction than any tool. 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 caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

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

It helps to separate the decision from the execution. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.

The checklist we ended up with:

1. Decide in advance what would make you stop
2. Write the constraint down before choosing a tool
3. Agree on what "done" means, in writing, before starting
4. Review the numbers monthly; change the targets rarely
5. Keep the feedback loop shorter than the planning cycle

The setup

The first thing to establish is what you are actually optimising for. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. The evidence here is thinner than anyone quoting it tends to admit.

Documentation is a symptom: you write it where the design is unclear. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. This is easier to write than to hold to when a deadline appears.

What looks like a process problem is frequently an ownership problem. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. There are organisations where the opposite is true, and they are not obviously worse off.

When to change course

Consistency is worth more than any individual improvement to slow living. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. A useful test: if this disappeared tomorrow, how long before anyone noticed?

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.

Feedback loops shorter than the planning cycle change everything. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. It is worth saying that we have not run this long enough to be confident.

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.