The Calendar That Lies to You
It's 8:47 on a Tuesday. You opened your calendar at 8:00 with a plan: ninety minutes blocked for the roadmap review that's been pushed twice, then an hour to actually read the architecture proposal your principal engineer sent Friday. By 8:47, both blocks are gone. A customer escalation landed in Slack at 8:12. A director needed a sign-off on a hiring exception by 9:00. Someone on your team is blocked on a decision only you can make, and they found you before coffee.
None of this was a bad choice. You didn't deprioritize the roadmap review. It simply lost, every time, to whatever arrived next. That's the part most managers misdiagnose. They assume the problem is discipline: if they just said no more often, protected the calendar more fiercely, this wouldn't happen. But discipline isn't the mechanism here. Reactive noise doesn't beat strategic work because you chose it. It beats strategic work because it arrives continuously, and strategic work doesn't arrive at all. Nobody pings you to remind you the quarterly plan needs attention. The escalation pings you itself.
The cost of that pattern now shows up in the data. Owl Labs' 2026 State of Hybrid Work report found that 74% of US workers do some work on Sundays, and 62% say AI has raised how much they're expected to finish in a day. Work that loses every weekday fight doesn't vanish. It moves to the weekend.
Volume isn't progress, either. Reuters' August investigation into Meta reported that internal code changes rose 220% year over year, while changes that reached users as new or improved features rose only 36%, and the time staff spent firefighting incidents rose 70%. A full calendar and a full commit log look the same from the inside. Neither tells you whether the quarterly objective moved.
If you've been in a VP Eng seat for more than a quarter, you've lived this exact week, probably more than once. The strategic objective you own is always "important." The incoming demand is always "quick." And "quick" wins almost every time, because it's the one with a deadline attached. That's the Escalation Tax: decisions that shouldn't have landed on your calendar land there anyway, and they charge you the time your actual job needed.
The fix isn't a better to-do list. It's a decision rule that runs before you engage with the demand at all, so you're not relitigating priority forty times a day.
Start with an honest audit of the current week. Not an idealized week, the actual one. Go block by block and label each one: reactive, meaning you're responding to something that arrived, or strategic, meaning you're moving something toward a quarterly objective under your own initiative. Most managers who do this for the first time are surprised by the ratio. It's rarely close to what they'd have guessed.
Then take this week's top five competing demands, the ones sitting in your inbox or your head right now, and run each one through two questions. Does this move a quarterly objective? And does only I have the authority or context to handle this? Two no's, and it's not actually yours to carry, however urgent it feels in the moment. One yes and one no still deserves a second look before you absorb it.
Here's what changes. The engineering director who needed that hiring exception signed off by 9:00 still gets an answer — just not from you. It turns out that decision never required your specific authority, only a decision. The customer escalation still gets triaged, fast, by the on-call process built for exactly this. What doesn't happen is the roadmap review getting bumped a third time. You protect a daily window, same time, before the reactive queue opens, and you run every new demand through the filter before it lands on your calendar instead of after.
The following Tuesday looks different, not because the inbox got quieter. It didn't. A demand that would have eaten 45 minutes of your morning gets redirected to the person who actually owns that decision, inside the first hour, because it failed both questions and you had the rule ready before you had the ping. The filter doesn't create time nobody has. It stops time from being taken without you noticing.
Here's the question worth sitting with: when you look at your calendar from the last two weeks, how much of it was actually your decision, and how much was just whatever arrived loudest?
Run that same two-question filter on your own calendar and you'll see the pattern. The Executive Escalation Assessment does that for you systematically — a free diagnostic, under 12 minutes, built to show you exactly which decisions on your desk fail both questions and shouldn't be there.
[blog link]
