Bridges wobble. Not because engineers got something wrong, but because they built the wobble in deliberately. Every major suspension bridge has what's called tolerance – a calculated amount of give, a fraction of its total load capacity held back on purpose. Use 100% of a bridge's strength and the first heavy lorry that crosses it tips the whole structure into crisis. The slack is the point.
Engineers Call It Tolerance
Engineers have known this for as long as bridges have existed. Ecologists know it too: a forest that uses every last drop of available water is one drought away from collapse, while the one that keeps a little in reserve just keeps going. Jazz musicians call it space – the notes you don't play, the half-beat of silence between phrases, the room left open so the next idea has somewhere to land. Take it away and the music becomes a noise.
The curious thing is that most people apply this principle beautifully to almost every system except their own life.
Why does a fully booked diary fall apart so fast?
Think about what a genuinely full week looks like. Every evening has something in it. Every weekend slot is claimed. The diary goes from Sunday night to Sunday night without a single afternoon that doesn't belong to something. On paper it looks productive, even impressive. In practice? It is the structural equivalent of loading a bridge to its absolute maximum and then watching nervously every time a pigeon lands on it.
The thing that gets lost when there is no slack is not rest exactly – it is response capacity. If you are booked solid and something goes wrong, or something unexpectedly good comes up, you have nothing to give it. You can't say yes to the friend who needs an afternoon, or to the idea that needs an hour of quiet thinking, because every available unit is already assigned. The bridge is full. The forest has drunk the well dry.
Slack Is Latent Time, Not Empty Time
What slack actually provides is not empty time. It is latent time – capacity that sits available, apparently doing nothing, quietly making everything else work. This is what makes the difference between a week that feels manageable and a week that feels like you're one cancelled train away from a complete unravelling. Writers who don't overschedule their mornings don't do less; they do better work. The people who keep one evening clear don't spend it staring at the wall; they spend it on the thing they couldn't have predicted needing that evening for.
None of this is laziness. It is structural intelligence. (There is a piece on a related idea in business, about how generous systems tend to outperform efficient ones, over at The Best Businesses Are Accidentally Generous.) The bridge engineer does not leave capacity unused because they can't be bothered to fill it. They leave it because they understand the difference between a system and a schedule.
How much slack should you leave in a working week?
The practical translation for an ordinary week is not especially dramatic. One lunch kept back. One evening that belongs to nobody. A commute with no podcast. Not enough to feel like you are doing less, just enough that the whole thing has somewhere to flex when the week stops being what you planned.
A system that runs at full stretch all the time is not efficient. It is fragile. The slack is not the bit you cut. It is what you are actually building the rest around.
Questions this raises
- Is unscheduled time actually more productive?
- Can you build slack into a job you do not control?
