Privacy Policy
We spent a quarter trying to get slow living right, and the useful lessons were not the ones we expected.
The first month
Speed and reversibility are the trade-off worth naming out loud. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. A useful test: if this disappeared tomorrow, how long before anyone noticed?
The interesting constraint is almost never the one in the brief. The first quarter shows the intended effect; the second shows what the intended effect displaced.
When to change course
Most of the difficulty lives at the boundaries, not in the middle. 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.
The default answer is right often enough to be dangerous. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. In practice the answer showed up in the calendar before it showed up in the dashboard.
You can have it fast, or you can have it reversible. Pick before you start, not after.
— Overheard in a retrospective
Where teams go wrong
Documentation is a symptom: you write it where the design is unclear. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
The compounding effects matter far more than the individual wins. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. When we mapped it out, four of the seven steps existed only to compensate for the second one.
A few things worth checking before you commit:
- Decide in advance what would make you stop
- 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
The setup
The first thing to establish is what you are actually optimising for. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. That said, none of this generalises cleanly across team sizes.
A shared definition of "done" removes more friction than any tool. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
A worked example
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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
What looks like a process problem is frequently an ownership problem. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. It is worth saying that we have not run this long enough to be confident.
If there is one thing worth carrying away, it is that the expensive mistakes in slow living are almost never technical ones.