Before You Schedule a Skip-Level, Ask This First
In brief
Senior leaders often feel an itch to sit down one-on-one with someone well below them on the chart. This essay treats that itch as a signal pointing at a specific problem, not a meeting to schedule before you know which one.
There's a specific itch that shows up in senior leaders soon after they pick up a second or third layer of reports: the pull to sit down, one-on-one, with someone well below them on the chart.
Manager Tools has shaped how I coach around this more than any other single source, and their read on the impulse is worth taking seriously. When one-on-ones are actually working up and down the chain, the itch for a skip-level shouldn't exist in the first place. If it shows up anyway, that's information.
Treat it as a signal, not a request to schedule. In practice it's almost always pointing at one of three things: you're not getting what you need through your normal line of communication with your own management chain, the manager in between isn't doing the job as well as the seat requires, or, underneath either of those, you don't fully trust that manager to carry the load. A leader running a clean system shouldn't need a skip-level to know any of this. The need itself is the tell.
Each of those calls for a different fix, and none of them is a meeting with someone else's direct report. A communication gap is structural: tighten what your own one-on-ones actually cover, so the reporting rhythm surfaces judgment and context rather than status updates. A performance gap calls for direct coaching aimed at the specific weakness — a skip-level just quietly routes around the manager while they wonder why they're suddenly being audited from above. Trust is the harder one. A skip-level doesn't repair it; it adds a workaround on top of a relationship nobody has fixed. Trust gets rebuilt where it broke, usually in a direct and sometimes uncomfortable conversation with the person you don't trust.
This is usually where the generic version disappoints the person on the receiving end — including, at times, me. I've felt this from that side of the desk, and heard the same thing from people I coach: someone tells you, in some form, that a skip-level is coming, and you quietly hope it will be about you, your growth, your trajectory, the thing you can't get traction on with your own manager. What actually shows up is a check-in. How's it going. Is there anything you need. Low-level and tactical, the kind of content that belongs in a regular one-on-one. You leave rehearsing what you said rather than sure it mattered, because the meeting ran on the leader's agenda and whatever was on their mind that week, not on you.
None of this makes skip-levels categorically wrong. They can genuinely earn their place when the motive is real, boots-on-the-ground curiosity about how the work actually happens, or real investment in one specific person's growth rather than a generic round of check-ins, or when the employee is the one who asked for it. Employee-requested skip-levels in particular can carry real upside for the person on the other side: visibility, a chance to learn how someone two levels up actually thinks. But even then, the same signal risk doesn't disappear. Going around a manager tells that manager something whether you intend it or not, and it's worth managing that consequence on purpose instead of pretending the meeting is neutral.
Most of the time, the discipline that pays is simple: before you schedule the meeting, name which of the three problems you're actually feeling, and go work on that one directly.
If you're a leader who keeps circling back to the idea of a skip-level and suspects, quietly, that the real issue is one specific relationship in your chain, that's a conversation worth having on its own: https://clients.agile-ideation.com/public/fit-conversation