What does it mean that recovery speed matters more than prevention?

You cannot prevent all disruptions but you can recover from them quickly.

Example: Two product managers experience the same disruption: a parent's hospitalization that consumes two full weeks of attention. Manager A returns home and spends six weeks circling — reopening her task list and closing it, skipping morning routines because they feel stale, telling herself she will get back on track Monday. Six Mondays pass. Manager B returns home and, the next morning, opens a single pre-written document titled 'Restart.' It tells her to do three things: process her inbox to zero, run one twenty-minute deep work block on her highest-priority project, and take a fifteen-minute walk. She does those three things. By day three she is running at 80 percent capacity. The disruption was identical. The recovery architecture was not.

Try this: Identify the last three times your routines were significantly disrupted — illness, travel, a family event, a work crisis, a move. For each one, estimate how many days elapsed between the end of the disruption and the point at which you were operating at roughly 80 percent of your normal capacity. Write those three numbers down. Now calculate the average. That is your current mean time to recovery. Next, for each disruption, write one sentence describing what slowed the recovery most. Look for patterns: was it guilt, decision fatigue about where to restart, loss of environmental cues, or something else? You now have a baseline and a diagnosis.