Your manager's calendar shows a meeting with their own boss every Tuesday at ten. You've never been in that room, and lately you've started wondering what actually gets decided in there — and whether anyone in it knows your name.
A skip-level meeting — sitting down with your manager's manager, without your manager present — is one of the few structured chances an ambitious employee gets to be seen by someone who genuinely influences their next role. Google's internal management guide, re:Work, recommends the practice on a quarterly cadence for exactly this reason: skip-levels surface information that a chain of command otherwise filters out before it reaches the top. Amazon runs a version of the same idea, documented in Working Backwards by former Amazon executives Colin Bryar and Bill Carr — senior leaders are expected to hold skip-level one-on-ones precisely because a single layer of management can quietly distort what reaches the people making resourcing decisions. Used well, a skip-level is a career tool. Used badly, it reads as an end run around the person who signs your appraisal.
The Room You're Actually Walking Into
Walk into a skip-level unprepared and you'll spend the first ten minutes discovering how little you know about what your manager's boss actually cares about. Senior leaders one or two levels up rarely think in the same units as your day-to-day manager: they're weighing headcount against next year's budget, watching which teams are quietly falling behind on delivery, and trying to work out which of the people two levels below them are ready to run something bigger. Your manager, by contrast, is mostly focused on this quarter's deliverables and keeping their own team functional. That mismatch is the entire point of the meeting — it's your one scheduled opportunity to speak in the language the room upstairs actually uses, rather than the version filtered down to you through your manager's day-to-day priorities. Treat the thirty minutes as a chance to answer questions that person is already asking about the wider team, not as a chance to talk about yourself for half an hour. The best skip-levels leave the senior leader with one clear, specific thing they didn't already know — a project stalled by a decision nobody above your manager has made yet, a risk building in a process only you can see from where you sit, or honest context on why a deadline slipped that your manager either didn't mention or didn't fully understand themselves.
When It Makes Sense — and When It's a Red Flag to Your Manager
A skip-level is not a promotion interview.
It works as a career habit when you use it for things genuinely outside your manager's reach: a cross-team dependency that only the senior leader can unblock, a strategic decision that's been sitting unresolved for months, or a standing practice the senior leader has explicitly invited (some UK finance and tech firms build quarterly skip-levels into onboarding for exactly this reason). It stops being a habit and starts being a warning sign the moment the timing tells its own story. Request one the week after a difficult performance conversation with your manager, or three weeks before the promotion cycle closes, and the senior leader will read the subtext whether or not you intended one. Three moments turn a routine skip-level into something that looks like an end run around your manager, and it's worth naming them plainly:
- Scheduling it within days of a disagreement or a difficult piece of feedback from your manager — the timing alone tells the story, regardless of what you actually planned to say.
- Using it to relitigate a decision your manager has already made and communicated, rather than to surface something new.
- Treating it as a substitute for a conversation you're avoiding with your manager directly — asking the senior leader to fix a problem that a five-minute talk with your own line manager would resolve, among other avoidance patterns worth watching for.
The Ask: What You Say to Your Manager Before You Say Anything to Anyone Else
Tell your manager first, always — not after you've already booked the meeting, and not as a courtesy heads-up sent the morning of. The wording matters less than the sequence. Something as simple as "I'd like to get thirty minutes with [name] to talk through the delivery risk on the platform migration — happy to loop you in on what I raise" does two things at once: it signals the topic is legitimate enough to say out loud, and it gives your manager the chance to add context, redirect you, or simply feel informed rather than blindsided. Managers who find out about a skip-level after the fact, from their own boss, rarely forget it — and the damage is disproportionate to almost anything you could actually say in the room. Frame the request around the topic, never around your manager's absence from your career progress; "I want visibility on the roadmap decision" lands very differently from "I feel like I'm not getting anywhere with you," even when both are technically true.
What to Do If Your Manager Says No
Some managers will hear the request and hesitate, and a few will say no outright. Before you decide that's a red flag about your manager, ask what's actually behind it — insecurity about their own standing is common, but so is a genuinely awkward moment upstream that you can't see, like a reorganisation being discussed two levels above either of you. Push back once, calmly, on the substance rather than the refusal: "Can you help me understand what's driving that? I'm not trying to go around you — I'm trying to get visibility on the platform migration timeline." If the answer is still no after that, most UK employers with a documented career-development policy (check your handbook or intranet before assuming there isn't one) give you a legitimate route to the same outcome — a formal mentoring scheme, a cross-functional project with senior sponsorship, or a skills conversation logged through your annual appraisal. Escalating over your manager's explicit refusal, rather than working one of those routes, almost always costs you more than the meeting itself would have gained. A manager who says no twice and watches you go around them anyway will remember that far longer than they'll remember whatever you actually wanted to raise.
Building an Agenda With Exactly Three Items
Three topics, no more. Arrive with them written down, and if the senior leader's assistant asks for an agenda in advance — common at director level and above in most UK corporates — send it the day before, not the morning of. A workable agenda mixes one item about a blocker outside your manager's control, one observation about the team that the senior leader wouldn't otherwise hear, and one question about direction: where the function is heading over the next two quarters, and what that implies for the skills worth building now. This works well in most flat, modern organisations — unless the senior leader habitually treats skip-levels as informal, unstructured chats, in which case turning up with a rigid three-point agenda can feel over-engineered rather than professional. Read the room in the first two minutes before you read from the framework. What you should never do is walk in without any structure at all and hope the conversation finds its own shape; a senior leader with fifteen minutes between back-to-back calls will remember the person who used the time well far more than the person who filled it.
The Three Ways Skip-Levels Backfire
Badmouthing your manager is the fastest way to burn the meeting and the relationship in one move. Senior leaders talk to the managers who report to them constantly, and even a mild complaint framed as "just context" tends to travel back in a distorted form within days. Asking the senior leader to make a call that's genuinely your manager's to make — a raise, a project reassignment, a schedule change — puts the senior leader in an impossible position and makes you look like you're shopping for a better answer rather than seeking one. And treating the whole exercise as a shortcut to promotion, rather than a source of useful information, shows within the first two sentences: senior leaders have sat through hundreds of these conversations and can tell the difference between someone building a relationship and someone angling for a title. None of these mistakes are fatal on their own the first time. Repeat any of them twice, though, and the senior leader starts declining the next request politely, which is worse than being told no outright — you never quite know why the door closed.
Closing the Loop Afterward
Go back to your manager within a day or two and share what came up, in outline rather than a full transcript. This isn't about surrendering the content of a private conversation — it's about closing the loop before your manager hears a secondhand version from someone else, which is how trust actually erodes in most working relationships. A short summary works: what you raised, what the senior leader said, and anything that might affect your manager's own priorities this quarter. Managers who see that you handle a skip-level with this kind of discretion tend to stop worrying about the next one, which is the entire point — the goal was never a single good meeting. It was permission to have more of them.