Terms Of Use
There is no shortage of advice about slow living. There is a shortage of advice that survives contact with a real week.
How it works
It helps to separate the decision from the execution. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. That said, none of this generalises cleanly across team sizes.
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 edge cases
Consistency is worth more than any individual improvement to slow living. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. It is worth saying that we have not run this long enough to be confident.
The second-order effects arrive about a quarter after the first-order ones. 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.
Every process is perfectly designed to get the results it gets.
— Overheard in a retrospective
Where to go deeper
There is a version of slow living that is mostly ritual. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.
The compounding effects matter far more than the individual wins. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
What we look for now:
- Write the constraint down before choosing a tool
- Review the numbers monthly; change the targets rarely
- Prefer the reversible option when the evidence is thin
- Decide in advance what would make you stop
- Name one person accountable — not a group
A common misreading
Nobody gets credit for the work that did not need doing. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The clearest signal was that people stopped asking where things were.
What looks like a process problem is frequently an ownership problem. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. This is easier to write than to hold to when a deadline appears.
Putting it together
The expensive mistakes here are rarely the technical ones. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
Most of the difficulty lives at the boundaries, not in the middle. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. A useful test: if this disappeared tomorrow, how long before anyone noticed?
The short version
The first thing to establish is what you are actually optimising for. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
If there is one thing worth carrying away, it is that the expensive mistakes in slow living are almost never technical ones.