I Had to Cancel Every 1:1 and Skip-Level I Run. A Month Later, I Am Still Flying Blind.

My calendar filled up with meetings this year until I had to cancel every 1:1 and skip-level I run. It has been a month. I have not fully wrapped my head around what that actually cost my team, and I am flying blind until I get them back on the calendar for September. I have spent real time with Copilot going through my own calendar and my team's actual needs, trying to build a strategy that genuinely protects this time and accounts for time zones on both sides, mine and theirs. I wrote the book on how to design exactly this kind of operating system, and I have already gone through that process with my own team, not just in theory. It still slipped past me. That detail is the part I keep sitting with.

The assumption most of us run on, myself included until this year, is that a packed calendar does not actually stop real communication. If something important comes up, in a 1:1, in a hallway conversation, in a message, people will make time for it or escalate it. The days are full because the work is real, and important things get raised regardless of how tight the schedule is.

Here is what that assumption misses. Raising something important does not just require some time. It requires a specific kind of time: room to go over, room for a pause, room for the conversation to breathe past its scheduled slot. A hard-stop meeting structurally signals exactly how much space exists, and that signal changes what people are willing to say before anyone consciously decides anything. A new hire calculates whether their question is worth the group's last three minutes and decides no. An introvert who needs a few extra beats to arrive at their point never gets there before the meeting ends. A real, messy problem that does not fit the status-update format gets compressed into "I'll open a ticket," because that is the only unit of communication the calendar structure has room for. None of this shows up anywhere. Leadership sees a calendar full of meetings and reads that as communication happening, while the actual signal, the harder-to-schedule, less tidy stuff, never surfaces in a form anyone can see was missing.

This is not a case for eliminating time-bounded meetings. Decisions genuinely need a hard stop to actually close, and an organization that never closes anything is its own kind of failure. Both needs are real, and neither one wins by being right. This is a structural bearing, not a villain to remove.

Managing this bearing means naming, deliberately, which category a given meeting belongs to: time-bounded and decision-forcing, or open-ended and disclosure-permitting. Left undeclared, the efficient, decisive default wins automatically, colonizing every slot on the calendar, including the ones meant to do something else entirely. A 1:1 or a skip-level exists specifically to hold the kind of time a hard stop cannot provide. When it gets scheduled and run the same way as a decision meeting, it loses the one job nothing else on the calendar can do. That is exactly what happened to mine this year, and getting them back on the calendar for September means restoring the one category of meeting that was never supposed to compete with the time-bounded kind in the first place, not simply closing a scheduling gap.

Look at your own calendar for next week. For each 1:1 or skip-level on it, is it actually protected as open-ended time, or has it quietly become a fifteen-minute status check with a hard stop? If you cannot tell the difference anymore, that is the answer.

I write about exactly this kind of structural gap, including the ones I am currently working through myself. Subscribe free: https://technicalleader.coach/daily-email

---

I write about structural leadership for technical leaders in high-stakes operating environments. If you're reading this outside the daily email, subscribe free: https://technicalleader.coach/daily-email