Systems compound; sprints don't
Two weeks of heroics buys you two weeks. A boring system you actually keep buys you the rest of the decade.
A sprint is a loan against next month’s energy. Sometimes you need the loan. But I have watched people — including me — run an entire company on borrowed weeks, and the interest is brutal.
The test I use: if I disappeared for two weeks, what would break?
Everything that breaks is a sprint wearing a system’s clothes.
Turning heroics into infrastructure
The move is almost never a bigger effort. It’s noticing the third time you do something by hand and refusing to do it a fourth time the same way. Three is the number for me. Once is chance, twice is coincidence, three times is a process nobody has written down yet.
When I catch the third repetition, I ask which of these it wants to be:
- A checklist — for work that needs judgment but keeps losing steps.
- A script — for work that needs no judgment at all.
- A default — for decisions I keep re-litigating with myself. Pick once, write it down, stop thinking.
Most of what feels like chaos in a small company is just a pile of decisions nobody has demoted to a default yet.
The unglamorous part
Systems are unsatisfying to build because they pay you later, quietly, in things that don’t happen. Nobody thanks you for the fire that didn’t start. You have to learn to feel an absence as a win, which is a genuinely acquired taste.
The way I keep the taste: once a month I write one line about something that used to eat a day and now takes ten minutes. Over a year that page is the most convincing evidence I have that the boring work is the real work.
