The Filter That Actually Separates Good Leaders From Burned-Out Ones
I learned about the unlikely to keep you up at night principle five years ago when I was running a product team that was drowning in meetings. We had seven syncs a day, a Slack channel that never slept, and every stakeholder felt entitled to our attention within the hour. I was exhausted, the team was churning, and I couldn't figure out why. The turning point came when my boss asked me a single question during our 1-on-1: "What is unlikely to keep you up at night?" It sounded dismissive at first, but he was forcing me to build a real triage system. Not the corporate nonsense version where everything is a priority. A literal filter. Here is how it works in practice. When a problem lands on your desk, you run it through a sequence of three questions before deciding how much time to allocate. Does it have real financial consequences? Can it be handled by someone on my team without my involvement? If it absolutely requires my attention, does it fall outside normal operating windows? Most issues fail at least two of those checkpoints and should be delegated, deferred, or ignored entirely. The reason this phrase became a weapon for the leaders I respect most is that it forces specificity. Vague worries are hard to dismiss. Financial impact, scope, and ownership are concrete. I started requiring my direct reports to label every escalation with which checkpoint it cleared and which it didn't. It cut our average meeting load from roughly fourteen hours per week down to about six. Nobody complained because the work that remained actually mattered.
I encountered a specific edge case that tested this framework. We had a compliance issue where a third-party vendor changed their data handling terms without proper notice. On paper, this was a legal risk. It was also completely outside our operational control. The legal team wanted me involved immediately. Using the filter, I determined the actual financial exposure was bounded by our contract terms at maybe twenty thousand dollars. The fix required a vendor renegotiation, not executive decision-making. I delegated the legal review to senior counsel, assigned my procurement lead to handle the vendor conversation, and tracked the outcome weekly. The whole thing resolved in eleven days. If I had taken it personally like I normally would have, it would have consumed three weeks of my attention and probably still gotten it wrong. The counter-intuitive part nobody talks about is that this filter gets harder to use as you get more senior. Your visibility increases, which means more things look like they could matter. You start noticing risk patterns that junior people miss. The filter doesn't become less useful. It becomes more demanding because you need better information to make the call. I solved this by building a lightweight signal pipeline. Any problem that reaches my desk gets tagged at intake with its category, estimated financial exposure, who owns the resolution, and a deadline window. I review these tags once a day rather than responding in real time. The difference between reacting and responding is usually one business day. There are legitimate failures with this approach. It does not work well in crisis situations where every signal matters simultaneously. During the 2023 supply chain disruptions, applying this filter literally meant ignoring problems that later compounded into real damage. I wish I had kept a longer leash on those situations. The workaround is simple: suspend the filter during declared emergencies and resume it within forty-eight hours after the immediate threat passes. You will catch things you missed during the pause.
Another pitfall is assuming your team applies the same filter rigorously as you do. They will not. Early versions of this system at my company failed because I delegated the filtering to managers who interpreted it as "ignore everything until it breaks." I fixed it by giving the filter a minimum floor. Every problem has to clear at least one checkpoint before it gets dismissed. If a problem fails all three questions, it gets logged in a shared tracker so it can be revisited later. This prevented the "set it and forget it" behavior that undermined the system initially. The implementation is straightforward. Create a simple intake form for any issue that reaches your team. Fields: description, estimated financial impact, current owner, proposed resolution path, and recommended action based on the filter. Set a daily review cadence. Track your pass-through rate. If you are clearing more than eighty percent of issues through delegation or deferral, you are probably being too aggressive. If you are clearing less than thirty percent, you are still doing too much hands-on work. The sweet spot I found across multiple teams was around fifty to sixty percent. This is not a perfect framework. It requires discipline, it adds a small administrative overhead, and it depends on having accurate information at intake. But the alternative is leading by reactivity, which is how you end up exhausted and wondering where the year went. The leaders I know who use this consistently are the ones who seem calm under pressure. They are not calmer people. They just have fewer things on their plate by design.
Get the Full Details
If you want to try it, start with your last week of decisions. Go back through your calendar and emails. For every issue you personally engaged with, ask whether it would have cleared the filter. Count how many you would have delegated or deferred. That number tells you how much headroom you have to actually use this system. Most people discover they have significantly more than they thought.
