Add a buffer or reserve

Hold protected slack that absorbs variability so shocks don't cascade.

Back-to-back is your default: the calendar is scheduled to 100%. So one overrunning call at 10am cascades, making you late to the 11, unprepared for the 1pm, answering messages during the 3, and by Thursday the week is rubble. No single meeting caused it. The absence of slack turned an ordinary wobble into a chain reaction.

Add a buffer or reserve holds protected slack that absorbs variability so shocks don't cascade. The cue: normal-sized disruptions producing outsized downstream damage because every resource, time, money, or energy, is committed to exactly 100%. Steps: find where variability actually enters (meetings overrun, urgent asks appear); insert protected slack at those points, 15 minutes between calls and two unbookable afternoon hours for overflow; then defend the buffer as a real commitment, because unprotected slack is just the first thing scheduled over. The word protected does the work: a buffer everyone can raid is not a buffer. The visible change: overruns die where they happen instead of propagating through the day, and Thursdays stop being rubble. Buffers cost capacity, though, so don't pad everything; oversized slack breeds waste, and buffering can mask a chronic overload that actually needs the workload itself renegotiated.