A packed timetable can look like proof of ambition, but a schedule with zero gaps is also a schedule with zero room for anything to go slightly wrong — and something always does.
What buffer time actually protects against
Buffer time isn't wasted time; it's insurance against the ordinary friction every week produces — a meeting that overruns, a task that takes longer than estimated, a commute delay. Without buffer, that friction doesn't stay contained to one slot; it pushes into the next one, and the one after that, until the whole day is behind.
The compounding effect of zero-gap schedules
A ten-minute overrun on a fully booked day doesn't cost ten minutes — it costs ten minutes plus whatever gets rushed or skipped later trying to catch up. Over a full week, this compounding is often the real source of the exhausted, always-behind feeling that leads to burnout, more than the actual workload does.
How much buffer is enough
A reasonable starting point is 10–15 minutes after any task or meeting longer than 45 minutes, and at least one fully unscheduled hour somewhere in each day. It will feel like "wasting" capacity at first — that discomfort is normal and worth pushing through for a couple of weeks before judging it.
Buffer time is not the same as free time
Don't fill buffer slots with more tasks just because they're technically open on the grid. Their entire value comes from being unclaimed — the moment you schedule something into them, they stop functioning as a shock absorber for the rest of the day.
Watch your weekly total, not just your daily one
A day can look reasonably paced while a whole week is still overloaded if every day is individually "fine" but back-to-back with no lighter days at all. Look at your timetable across the full week and make sure at least one day has meaningfully more breathing room than the rest.