The Meeting Nobody Explains How to Use
Somewhere between your first performance review and your fifth, someone mentions "skip-level" in passing, and you nod like you know what happens in one. Most people don't. A skip-level is simply a conversation with your manager's manager, without your manager in the room — and the fact that it sounds slightly illicit is exactly why so few people use it well. You either avoid it entirely, worried it looks like you're going over someone's head, or you walk in and treat it like a confessional, unloading every frustration you've been sitting on for six months. Both approaches waste one of the few structured chances you get to be visible to someone who actually influences your promotion, your raise, and your next role — and who almost never sees your work directly.
What It's Actually For
A skip-level exists to give a senior leader visibility into how their org runs below the layer they normally see, and to give you fifteen or thirty minutes of attention from someone who signs off on headcount and budget decisions that shape your career. It is not a grievance channel. It is not therapy. And it is absolutely not the place to relitigate a disagreement you already had with your manager last week — if you bring that in, the skip-level walks away thinking you're a source of friction, not talent worth investing in. Companies like Google and Intuit have run skip-levels as a standard part of their management cadence for years precisely because they catch what direct-report chains filter out: a strong performer who's quietly flight-risk, a bottleneck nobody's named yet, a team that's about to lose its best engineer over a comp gap nobody escalated.
Reading the Room Before You Ask for One
Check whether skip-levels already exist as a norm on your team before you request one cold. Some managers schedule them quarterly for everyone; others have never heard the term and will assume you're building a case against them the second you ask. If your company runs an engagement survey or has an HRBP, that's your fastest way to find out — a two-line message to HR asking "does our org do skip-levels, and how do people usually request one" reads as due diligence, not scheming. If skip-levels genuinely don't exist as a practice, don't invent the format yourself by cold-emailing a VP. Ask your manager directly: "I'd like to get some time with [name] at some point — is that something people here do, and would you mind if I set it up?" Most reasonable managers say yes immediately, because refusing makes them look like they have something to hide.
Timing matters more than people think. Book the skip-level in the two or three weeks after you've shipped something visible — a launch, a closed deal, a process fix that saved the team real time — not during a slow stretch when you have nothing concrete to point to and nothing but complaints to fill the silence. A skip-level booked the week after your manager tells you "great quarter" lands completely differently than one booked the week after a missed deadline. Sequence it that way on purpose. The senior leader you're meeting almost certainly has fifteen other things pulling at their attention that day, and the version of you that shows up with one sharp, recent example is the version they remember six months later when a role opens up.
What to Actually Say in the Room
Walk in with three things: one concrete accomplishment with a number attached, one honest observation about the team or the work that a senior leader wouldn't otherwise hear, and one specific ask. Skip the small talk beyond thirty seconds — they know why you're there, and burning ten minutes on pleasantries in a thirty-minute slot is the single most common way people waste this meeting. "I led the migration that cut our deploy time from 40 minutes to 6" lands. "I've been working really hard and taking on a lot" does not, because it gives the leader nothing to remember or repeat to anyone else. Bring the honest observation even if it's slightly uncomfortable: maybe the team is under-resourced for the roadmap it's been handed, maybe a process everyone quietly hates is costing real hours every sprint. Frame it as information, not complaint — "here's something I don't think reaches you normally" — and let them decide what to do with it.
Name the ask. This is the part almost everyone skips, and it's the part that actually changes outcomes.
The ask can be small: "I'd love visibility into how the leadership team thinks about headcount for our group next year." It can be direct: "I'm aiming for a promotion to senior by Q2 — what would you want to see from someone at that level?" It can even be a request for a specific connection: "I'm interested in the platform team's roadmap — is there someone over there worth talking to?" What it cannot be is nothing. A skip-level that ends with "well, thanks for the time, this was great" and no actual ask registered is a meeting the leader forgets by lunch. Ask for something real. Worst case, they say no or "let me think about it" — and you've still made your name and your work specific in their memory instead of generic.
The Nuance Nobody Mentions
Here's the part that complicates the advice above: in a genuinely dysfunctional org, a skip-level can backfire even when you do everything right. If your manager is insecure or territorial, they may hear about the meeting — skip-levels are rarely as confidential as they're advertised — and treat it as a threat regardless of what you actually said in the room. There's no clean fix for that scenario beyond reading your specific manager correctly before you request the meeting at all; in a healthy team, transparency about wanting a skip-level builds trust, and in a fragile one, the same transparency can cost you. Know which team you're on before you walk in with a script built for the healthy version.
The Follow-Up That Makes the Meeting Count
Send a short note within 24 hours — three sentences, not a memo. Thank them for the time, restate the ask in one line so it's written down somewhere, and mention one thing from the conversation that stuck with you. This is not optional politeness; it's the mechanism that turns a pleasant fifteen minutes into something the leader actually remembers and can act on. Most people who do skip-levels well request them again on a rough cadence — every two quarters is realistic for most orgs — and treat each one as a data point building toward the same goal rather than a one-off event. Track what you said you'd follow up on, because the leader almost certainly won't, and showing up to the next one having delivered on your own ask is worth more than any single line you say in the room.
Don't treat a skip-level as a substitute for a good relationship with your actual manager, and don't use it to route around a conversation you're avoiding having with them directly. The two channels do different jobs: your manager decides your day-to-day scope and writes your review; your skip-level shapes whether you're on the list when a bigger opportunity opens two levels up. Use both, keep them honest with each other, and the fifteen minutes stop feeling illicit and start feeling like exactly what they are — one more tool for making your work visible to the people who decide what happens to it next.