7 small changes that improve 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.

How we knew it was working

A shared definition of "done" removes more friction than any tool. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. That said, none of this generalises cleanly across team sizes.

Consistency is worth more than any individual improvement to slow living. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. The clearest signal was that people stopped asking where things were.

The compounding effects matter far more than the individual wins. Slow living rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. In practice the answer showed up in the calendar before it showed up in the dashboard.

The part that surprised us

Speed and reversibility are the trade-off worth naming out loud. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.

The interesting constraint is almost never the one in the brief. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

The default answer is right often enough to be dangerous. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

The numbers

Scope is the variable everyone adjusts last and should adjust first. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. The evidence here is thinner than anyone quoting it tends to admit.

The tooling question is downstream of the constraint question. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The version of this that works fits on an index card. The version that fails needs an onboarding session.

Measurement is usually where this falls apart. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

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

— Overheard in a retrospective

What we look for now:

1. Decide in advance what would make you stop
2. Prefer the reversible option when the evidence is thin
3. Keep the feedback loop shorter than the planning cycle

What we tried first

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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

Most of the difficulty lives at the boundaries, not in the middle. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.

What changed

The second-order effects arrive about a quarter after the first-order ones. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.

The first thing to establish is what you are actually optimising for. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.

It helps to separate the decision from the execution. 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. Set a date at which you will stop, and write down in advance what would make you stop earlier.

The situation

Nobody gets credit for the work that did not need doing. 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 useful test: if this disappeared tomorrow, how long before anyone noticed?

Feedback loops shorter than the planning cycle change everything. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

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

Where it still breaks

Consider the failure mode rather than the success case. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. When we mapped it out, four of the seven steps existed only to compensate for the second one.

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.