Slow living, explained without the jargon

Most teams arrive at slow living the same way: something breaks, and the fix becomes a habit.

Where it still breaks

Feedback loops shorter than the planning cycle change everything. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

It helps to separate the decision from the execution. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

The numbers

The tooling question is downstream of the constraint question. Slow living rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.

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.

The first thing to establish is what you are actually optimising for. 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.

What it cost

Measurement is usually where this falls apart. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.

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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

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

— Overheard in a retrospective

What changed

The second-order effects arrive about a quarter after the first-order ones. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. The clearest signal was that people stopped asking where things were.

Consider the failure mode rather than the success case. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. This is easier to write than to hold to when a deadline appears.

The default answer is right often enough to be dangerous. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. The evidence here is thinner than anyone quoting it tends to admit.

What we look for now:

1. Write the constraint down before choosing a tool
2. Name one person accountable — not a group
3. Agree on what "done" means, in writing, before starting

What we would do differently

The compounding effects matter far more than the individual wins. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.

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.

The part that surprised us

Documentation is a symptom: you write it where the design is unclear. 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. A useful test: if this disappeared tomorrow, how long before anyone noticed?

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

There is a version of slow living that is mostly ritual. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.

How we knew it was working

The interesting constraint is almost never the one in the brief. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.

The expensive mistakes here are rarely the technical ones. 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. 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 caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

What we tried first

Scope is the variable everyone adjusts last and should adjust first. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.

None of this generalises perfectly. Take the parts that map onto your constraints and discard the rest — that is what the framing is for.