Take a Break!

Your brain has a trick it likes to play right before a break. Whatever you are working on suddenly becomes the most important thing you have ever touched. Too important to put down. Definitely too important to leave for a week. Charles, Igor, and I have watched this trick work on us more times than any of us would like to admit.

Here is the problem: the feeling never goes away. Next month's project will feel exactly this critical. So will the one after that. Urgency is not a property of the work. It is a property of your proximity to it. Stand close enough to anything and it fills your entire field of view.

The motivations underneath the trick are worth naming, because they are rarely about the work either. Some of us need to feel needed. Some of us are afraid of finding out the team runs fine without us — or afraid that it won't. Some of us have quietly wired our identity to our output, so stepping away feels like disappearing. None of these are reasons to skip a break. They are reasons to take one.

The bill comes due either way. Defer downtime long enough and the costs show up everywhere: in your body, in your mood, in the conversations you stop having with the people who live in your house. Tara Haelle wrote a great piece on Medium about surge capacity — the reserve we draw on to keep functioning in a crisis — and why you feel awful when it runs dry. You cannot run on surge capacity forever. You only get to choose whether you stop on purpose or by force.

That is the real distinction: intentional downtime versus accidental downtime. Accidental downtime is the sick day your body files on your behalf. It is the evening you spend on the couch, technically home, functionally gone. It restores nothing because it was never designed to restore anything. Intentional downtime is scheduled, protected, and taken before you need it, not after.

A few guardrails hold up even on a busy schedule, whether you run a team or contribute on one. Put the break on the calendar first and schedule the work around it, not the other way around. Decide before you leave what actually counts as an emergency, and name the person who handles everything else — if anything can interrupt you, you never really left. Shrink the unit if you must: one full day with your phone in a drawer beats a week where you check email every morning. And if you lead people, go first and go loudly. Your team does not take its cue from the vacation policy. It takes its cue from whether you replied to email from the beach.

One more thing for when you come back: tell your team what you did. Sharing your break turns out to build trust rather than erode it — more on that in the trip report.

The work will still be there when you get back. It always is. Whether you are still any good at it depends on whether you actually left. ∎