3 things nobody tells you about slow living

The interesting thing about slow living is how rarely the hard part is the part everyone prepares for.

Where teams go wrong

Scope is the variable everyone adjusts last and should adjust first. 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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

Speed and reversibility are the trade-off worth naming out loud. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. In practice the answer showed up in the calendar before it showed up in the dashboard.

Feedback loops shorter than the planning cycle change everything. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. The version of this that works fits on an index card. The version that fails needs an onboarding session.

When to change course

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. It is worth saying that we have not run this long enough to be confident.

Measurement is usually where this falls apart. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.

The default answer is right often enough to be dangerous. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.

A worked example

Consider the failure mode rather than the success case. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. When we mapped it out, four of the seven steps existed only to compensate for the second one.

The compounding effects matter far more than the individual wins. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.

Simplicity is not the absence of work. It is the result of it.

— Overheard in a retrospective

Making it stick

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.

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

The first month

The tooling question is downstream of the constraint question. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.

A shared definition of "done" removes more friction than any tool. 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.

A few things worth checking before you commit:

• 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
• Prefer the reversible option when the evidence is thin

Choosing what to measure

Consistency is worth more than any individual improvement to slow living. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. That said, none of this generalises cleanly across team sizes.

The first thing to establish is what you are actually optimising for. Slow living rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. A useful test: if this disappeared tomorrow, how long before anyone noticed?

There is a version of slow living that is mostly ritual. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next.

Start with the constraints

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 expensive mistakes here are rarely the technical ones. The first quarter shows the intended effect; the second shows what the intended effect displaced. The evidence here is thinner than anyone quoting it tends to admit.

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.

Handing it over

What looks like a process problem is frequently an ownership problem. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

The short version: decide what you are optimising for, write it down, and revisit it when the answer stops feeling obvious.