Rebuilding our approach to slow living

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

The one people skip

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.

Consider the failure mode rather than the success case. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. The evidence here is thinner than anyone quoting it tends to admit.

The one that only matters at scale

The default answer is right often enough to be dangerous. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.

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. There are organisations where the opposite is true, and they are not obviously worse off.

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

The habit that compounds

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

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. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

The tooling question is downstream of the constraint question. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.

Every process is perfectly designed to get the results it gets.

— Overheard in a retrospective

Where to start on Monday

A shared definition of "done" removes more friction than any tool. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. In practice the answer showed up in the calendar before it showed up in the dashboard.

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. That said, none of this generalises cleanly across team sizes.

The checklist we ended up with:

1. Prefer the reversible option when the evidence is thin
2. Name one person accountable — not a group
3. Decide in advance what would make you stop

Begin with the obvious one

Most of the difficulty lives at the boundaries, not in the middle. The first quarter shows the intended effect; the second shows what the intended effect displaced.

There is a version of slow living that is mostly ritual. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. This is easier to write than to hold to when a deadline appears.

Feedback loops shorter than the planning cycle change everything. Slow living rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. Set a date at which you will stop, and write down in advance what would make you stop earlier.

The quiet win

Scope is the variable everyone adjusts last and should adjust first. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

Speed and reversibility are the trade-off worth naming out loud. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.

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

Measurement is usually where this falls apart. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

The interesting constraint is almost never the one in the brief. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. The version of this that works fits on an index card. The version that fails needs an onboarding session.

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