What Leaders and Managers Can Learn from The Sleep Revolution
It's 11:45 p.m. and the manager sends a project update to the whole team with "just wanted to get this off my plate before tomorrow." Nothing in it needed to happen tonight, but the green dot next to her name at that hour reads, to everyone watching, as proof of how seriously she takes the work. Senior leadership notices too, and quietly files her as someone who can be counted on for anything, at any hour. What she doesn't see is that two direct reports, not wanting to look less committed, start drafting their own late-night replies, and the team's actual working hours begin drifting later without anyone deciding that on purpose. The trap is mistaking your own visible exhaustion for leadership, when it's actually just setting the culture your team will feel obligated to match. Once you notice that your hours are a policy whether you intend them to be or not, the question becomes what you're actually modeling.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Exhaustion as a leadership credential
Sending messages at odd hours can feel like proof you're carrying real weight, and organizations often reward exactly that visibility. But a leader's clear thinking is worth more to the team than a display of hours, and the two are not the same thing.
A manager sends an update at 11:45 p.m. with "just wanted to get this off my plate," and two direct reports, wanting to seem equally committed, start drafting their own late-night messages, even though nothing needed to happen before morning.
For a week, draft any late-night message you'd normally send immediately, then schedule it to go out during work hours instead.
How your visible hours become your team's culture
Teams read what leaders do, not what they announce, so a boundary you state but don't keep teaches the opposite lesson. Your calendar, your send times, and your away messages are policy documents whether you meant them that way or not.
A manager tells the team "nobody needs to answer emails after six," then replies to a minor thread at nine that same night, and the team quietly concludes the real rule is whatever she actually does.
Change one visible behavior — your send times, your calendar block, your status — before you say anything new to the team about it.
Protecting sleep as a leadership decision, not a personal indulgence
Treat your own sleep the way you'd treat a direct report's wellbeing: as something a good leader manages deliberately, not as slack in the schedule that absorbs any new demand.
A manager blocks an early bedtime on her calendar but tells her assistant to interrupt it for anything "leadership needs," which turns out to include nearly everything, so the block never protects a single evening.
Name one category of request that does not get to interrupt your sleep window this month, and hold it even once.
Re-defending the boundary through every reorg and crunch
Every reorg, every budget cycle, and every new initiative from above generates a fresh, reasonable-sounding case for why this particular week is the exception. Holding the line as a manager means re-asserting the same boundary at each new pressure point, because your team is quietly watching whether it survives contact with real demands or only existed when things were calm.
Being the buffer between senior leadership and your team can pull directly against protecting your own sleep — the workload above you doesn't shrink just because you stop absorbing it into your evenings. The answer isn't heroic absorption; it's making the tradeoff visible upward, telling your own manager plainly what your team can't take on this week rather than quietly eating the difference yourself. A rested leader who pushes back once is more useful to a team than an exhausted one who says yes to everything.
Name one thing, honestly
Where in your calendar this week would a direct report see your actual priorities, and does protecting your sleep show up anywhere on it?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Name one category of request that does not get to interrupt your sleep window this month, and hold it even once.