What slow living actually means

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

How we knew it was working

Nobody gets credit for the work that did not need doing. 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.

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.

Where it still breaks

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. A useful test: if this disappeared tomorrow, how long before anyone noticed?

The tooling question is downstream of the constraint question. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

What we would do differently

Consistency is worth more than any individual improvement to slow living. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

The compounding effects matter far more than the individual wins. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. In practice the answer showed up in the calendar before it showed up in the dashboard.

Most of the difficulty lives at the boundaries, not in the middle. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. It is worth saying that we have not run this long enough to be confident.

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

— Overheard in a retrospective

The part that surprised us

The default answer is right often enough to be dangerous. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next.

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.

The expensive mistakes here are rarely the technical ones. 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. That said, none of this generalises cleanly across team sizes.

The checklist we ended up with:

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

What changed

Scope is the variable everyone adjusts last and should adjust first. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

A shared definition of "done" removes more friction than any tool. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.

Measurement is usually where this falls apart. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

What it cost

The interesting constraint is almost never the one in the brief. 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. 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.

What we tried first

The second-order effects arrive about a quarter after the first-order ones. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.

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

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