Field Notes · Practice

The Untouchable Day

7 min read · organizational behavior

Not a day off. A day in the building where you have no day-to-day responsibilities.

Look at your calendar from six months ago. Find a day that was set aside, in advance, for thinking about where the company is headed rather than what it needs from you right now. If you can't find one, you're not unusual. You're the norm the research keeps describing, and it's worth naming precisely what's missing, because "I need more time" is too vague to act on and "I need a vacation" is the wrong prescription. What's missing isn't rest. It's a day, still at your desk, still reachable in an emergency, where you get to think...and think.

The tyranny of the urgent

In 1967, missionary and seminary president Charles Hummel wrote a short essay that gave this problem its name: the tyranny of the urgent. His argument was simple and has outlived its original context by decades: urgent tasks announce themselves and demand instant action, while important tasks, the ones that actually determine where you end up, rarely announce themselves at all. Left alone, the urgent always wins, not because it matters more, but because it's louder.

Dwight Eisenhower is widely credited with the sharper version of the same idea, the line that eventually became a productivity framework with his name on it:

What is important is seldom urgent, and what is urgent is seldom important.Often attributed to Dwight D. Eisenhower

Peter Drucker, writing in The Effective Executive, drew the same line between two things that get treated as synonyms and aren't:

Efficiency is doing things right; effectiveness is doing the right things.Peter Drucker, "The Effective Executive" (1967)

A week that's entirely reactive can be extremely efficient and still be pointed nowhere in particular.

What CEOs actually do with their time

Harvard Business School's Michael Porter and Nitin Nohria spent years having CEOs and their assistants log their calendars in fifteen-minute increments, real time-use data, not self-report. The pattern that emerged was consistent: the people ultimately responsible for their company's long-term direction spent the overwhelming majority of their week absorbed in operational demands, meetings, reviews, people problems, the next fire, and only a sliver of it on the long-range, structural questions that were, on paper, the reason the job existed. Nearly every CEO in the sample said long-term strategy was the most important part of the role. Almost none of their calendars reflected that belief.

This isn't a discipline problem. It's what happens by default when nothing is structurally protected. Time doesn't stay open on its own; it gets filled by whoever asks for it loudest, which is rarely your five-year plan.

Why stepping back actually works, cognitively

There's a reason "sleep on it" is good advice and not just a cliché. A 2009 meta-analysis by Ut Na Sio and Thomas Ormerod, pooling dozens of studies on problem-solving, found that deliberately stepping away from a hard problem, an incubation period, measurably improved performance when people came back to it, particularly on the kind of open-ended, creative problems that strategy actually is (as opposed to problems with one clean right answer). Your brain keeps working on the problem in the background in a way that grinding through it directly doesn't allow.

Separately, organizational psychologists Sabine Sonnentag and Charlotte Fritz have spent years studying what they call psychological detachment, the ability to mentally disengage from work demands rather than just physically leaving the building. Their research links genuine detachment, even briefly, to better next-day mood, lower exhaustion, and more proactive, creative behavior at work. The mechanism is almost boring in its simplicity: a mind that's constantly on-call for the next operational demand never gets the conditions it needs to do anything else.

The strategic mind is not tired from lack of hours. It's tired from lack of a single hour that wasn't spoken for by someone else's problem.

You don't need a cabin in the woods

Bill Gates's twice-yearly "Think Week," a week alone reading and writing about where technology was headed, became famous partly because it was so extreme relative to a normal executive's schedule. But the extremity is the least useful part of the example. The useful part is smaller and far more replicable: a block of calendar time, defended in advance, in which the only agenda is the big picture, not a retreat, not a vacation, not time away from the company. If anything, it's time more fully inside the company than any status meeting gets you.

That's the model worth copying, scaled down to something that is affordable: one day, still in the office, phone still on for genuine emergencies, calendar blocked the same way a board meeting would be blocked, because a board meeting doesn't get bumped for a vendor call and this shouldn't either. Not a day off from work. A day off from the tyranny of whatever's loudest.

What tends to actually protect it

Here's the uncomfortable part: almost nobody holds this boundary for themselves, for the same reason almost nobody hits "ignore" on their own fire alarm. The urgent thing feels like it has permission to interrupt precisely because you're the one deciding whether to let it. The executives who actually keep an untouchable day tend to have one thing in common: someone else, with real authority over the calendar, whose job includes saying no to the interruption on their behalf, on the days it isn't actually an emergency. That's a structural fix, not a willpower fix, and it's a large part of what a Chief of Staff is actually for.