A post-mortem on our slow living rollout

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

The setup

Scope is the variable everyone adjusts last and should adjust first. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

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

Where teams go wrong

Feedback loops shorter than the planning cycle change everything. 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. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

The interesting constraint is almost never the one in the brief. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.

A worked example

Consider the failure mode rather than the success case. 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. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.

The cost of a bad decision is rarely the decision. It is the six months of building on top of it.

— Overheard in a retrospective

Choosing what to measure

The second-order effects arrive about a quarter after the first-order ones. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. Set a date at which you will stop, and write down in advance what would make you stop earlier.

A shared definition of "done" removes more friction than any tool. The first quarter shows the intended effect; the second shows what the intended effect displaced. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.

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.

The checklist we ended up with:

• Prefer the reversible option when the evidence is thin
• Keep the feedback loop shorter than the planning cycle
• Write the constraint down before choosing a tool

Handing it over

Measurement is usually where this falls apart. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.

Documentation is a symptom: you write it where the design is unclear. Slow living rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. The version of this that works fits on an index card. The version that fails needs an onboarding session.

The expensive mistakes here are rarely the technical ones. 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.

Start with the constraints

The tooling question is downstream of the constraint question. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.

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. The evidence here is thinner than anyone quoting it tends to admit.

The first month

Most of the difficulty lives at the boundaries, not in the middle. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.

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

When to change course

The compounding effects matter far more than the individual wins. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.

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.

Making it stick

Nobody gets credit for the work that did not need doing. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.

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