5 min read
The best skip-level meeting questions surface what your direct reports are too senior to tell you and what your skips are too junior to volunteer. The list below is organized by what you’re actually trying to find out: how the work is going, how their manager is doing, where their career is going, and the questions that just create awkwardness if you ask them.
The Compression Check.
A concept from No Self Limits. Information traveling up a management chain compresses at every layer. Your direct reports’ managers summarize, prioritize, and sometimes filter what they pass to you, which is mostly necessary, occasionally biased, and always partial. The skip-level meeting is the audit on that compression. Done well, it tells you what was lost in translation. Done poorly, it just makes everyone wary.
QUICK ANSWERS
What is a skip-level meeting?
A meeting between you and someone two levels below you in the org chart, without their direct manager present. Usually 30 to 45 minutes, typically a 1-on-1.
How often should you do skip-levels?
Every direct report of every direct report should get one every six months at minimum, ideally every quarter. Higher frequency than that strains the manager-in-the-middle.
Should you tell their manager about it?
Yes, before you book it. Surprising a peer manager with skip-levels is the fastest way to make them defensive and pollute the data you’d get.
What’s the actual goal?
Find out what the layer below you sees and is blocked on, separate from what their manager has decided is worth escalating. It’s a calibration check, not a back-channel.
What skip-level meetings are actually for
The honest purpose of a skip-level is to check the compression on what your direct reports’ managers are telling you about their teams. Three things compress at every management layer: priorities (what gets brought up), context (what gets summarized), and sentiment (what gets softened). A good skip-level surfaces all three so you can recalibrate.
A skip-level is not a back-channel for complaining about their manager, a vehicle for skipping over your direct report when you don’t trust them, a fishing expedition for HR-relevant data, or a place to deliver feedback about their manager’s performance. If you’ve got a problem with a peer manager, skip-levels are not the place to investigate it. They become useless once your skips realize that’s what they’re for.
Skip-level questions about the team and the work
These surface what’s going on in the actual work, distinct from what your direct report has summarized in your weekly 1-on-1.
- What’s a project that’s not officially a priority but is taking up most of your week?
- What did this team used to do that we stopped doing, and what changed because of it?
- Who on the team is doing work that nobody knows about?
- What’s a meeting on your calendar that should not exist?
- What process here is everyone working around instead of through?
- Where do you spend time waiting on something that you used to not have to wait on?
- What’s a customer or stakeholder pattern you’ve noticed that hasn’t been written up anywhere?
Skip-level questions about how they work with their manager
These are the most sensitive. Done wrong, they read as fishing for grievances. Done right, they tell you whether the manager-in-the-middle is doing the things you can’t observe directly. Notice that none of them ask “is your manager good.” Behaviors are observable and actionable; opinions are not.
- What kind of feedback do you get most often from your manager, and is it useful?
- What’s something you’ve tried to escalate that didn’t make it past your manager?
- When was the last time your manager changed their mind based on something you said?
- What would you want your manager to do less of?
- What would you want them to do more of?
- How does your manager handle disagreement on the team?
Skip-level questions about them, their growth, and their career
These are the ones their manager probably should be asking but might not be, or might be asking poorly.
- What part of your job do you wish you had more time for?
- What part do you wish you spent less time on?
- What skill have you been trying to develop, and where are you stuck?
- Where do you see yourself in this org in 18 months?
- What would have to be true for you to still be on this team in three years?
- Is there a role on another team you’d want at some point, and what’s keeping you from going for it?
The five questions to avoid
- “How are things going?” Too open. They will say “fine.”
- “What do you think of [their manager]?” Sets a trap. They either lie or burn a bridge.
- “What can I help with?” Puts the labor of identifying their problem on them. They don’t know what you can help with.
- “Any concerns?” Same trap as #20 with more anxiety attached.
- “What’s going wrong?” Too negative. You’ll get either nothing or a flood you can’t act on.
One last question worth asking
25. “What’s a question I should be asking you that I haven’t?” This is the catch-all. It surfaces things outside the categories above and tells you what they actually wanted to talk about coming in. The best version of this question always lands, even with people who were quiet for the first 25 minutes.
How to use what you learn from a skip-level
Whatever you hear, the cardinal rule is this: never bring it back to their manager in a way that identifies the source. If a skip-level reveals a real pattern that needs addressing, raise the pattern with the manager generically. “I’m hearing that escalations from your team are slow to make it up. Walk me through how that pipeline works.” Never: “Your direct report told me you sit on escalations.”
If your skip-levels become known as the reason their manager just got dressed down, the channel is dead inside a month, and you’ll never get clean signal from that team again.
FAQ for managers running skip-levels
How do you handle it when a skip-level reveals a real problem with their manager?
Address the problem generically with the manager, not the source. If three skips mention slow escalation, you can raise the slow-escalation issue without saying who said what. The trick is treating skip-levels as pattern-detection, not evidence-gathering. If you find yourself naming sources to make a case, you’re using the channel wrong and it’ll close fast.
Should skip-levels be 1-on-1 or group?
1-on-1 by default. Group skip-levels turn into theater because nobody wants to say anything sensitive in front of a peer who reports to the same person. Reserve group formats for kickoffs or specific decisions, not for calibration.
What if the person is nervous and won’t say anything substantive?
First skip-level with someone is almost always polite and surface-level. The skill is taking the surface answer and asking the next question down. Not “what’s the team like” but “what’s a meeting that shouldn’t exist.” Concrete, behavior-anchored questions get behavior-anchored answers. Repeat skip-levels open up because trust accrues across meetings, not within one.
Should you take notes during a skip-level?
Light notes are fine, full transcript is not. The person needs to know what you write isn’t going into a system their manager can read. If you’re going to write anything down, say so explicitly: “I’m going to jot a couple of phrases so I don’t forget, this isn’t going anywhere.” Verbatim notes change the room.
How long should a skip-level last?
30 to 45 minutes. Anything shorter is a check-in, not a calibration. Anything longer becomes a therapy session, which the person may want but won’t help you do your job.
Questions readers ask
FAQ for people preparing for a skip-level
What is a skip-level meeting and why does it exist
A skip-level meeting is a one-on-one between you and your manager’s manager. The format is the same as any 1:1. The dynamic is different. You’re talking to the person who decides whether your manager gets promoted, fired, or pushed laterally.
The reason it exists is that information compresses going up the chain. Your manager filters what reaches their boss. Sometimes that filter is fair. Sometimes it isn’t. The skip-level is the formal mechanism for sending signal directly, without the filter.
How often should skip-level meetings happen
Once a quarter is the floor at most companies. Once a month is rare and usually only happens in flat orgs or on small teams. If your skip-level is happening twice a year, you’re likely getting less of one than the org intends.
Cadence matters less than what you do with it. A quarterly skip-level you treat seriously is worth more than a monthly one where you tell your boss’s boss everything is fine.
Should I tell my manager I’m having a skip-level
Yes. Surprising your manager that you went around them creates a problem that didn’t need to exist. The meeting is on the calendar anyway. Mention it casually in your next 1:1 and treat it as a normal organizational thing, because that’s what it is.
The exception is if you’re meeting with the skip-level specifically because something has gone wrong with your manager and HR is involved. That’s not a skip-level. That’s an HR conversation, and the rules are different.
What is the difference between a skip-level and a regular 1:1
A 1:1 is about your work and your manager’s relationship with it. The agenda is operational. The skip-level is about you in the org, not you in the work. The agenda is strategic.
Practical translation: don’t bring your sprint blockers to the skip-level. Bring questions about where the org is going, what they’re looking for in the next round of leadership hires, and how the team is being read from one level up.
What if I have nothing to say in a skip-level
You always have something to say. The fear comes from a false belief that you need a major problem or a major win to justify the time. You don’t. You need one good observation and three good questions.
Observation: a pattern you’ve noticed in the team that your skip-level might not see from one level up. Questions: where the org is going, what they’re worried about, what they think you should be paying attention to. That’s a 30-minute meeting.
What if my skip-level cancels or no-shows repeatedly
It happens. Skip-levels are senior, calendars are brutal, and you’re rarely the most urgent thing on their day. Reschedule once, no comment. Reschedule twice in a row, escalate gently through your manager: “I keep getting bumped, can we find a slot that’s more likely to stick.”
If you can’t get a real skip-level for two quarters running, that’s a real signal about how the org views you, your function, or your manager. Treat the pattern as information, not as a personal slight.
Can I talk about my manager in a skip-level meeting
Carefully and rarely. Skip-levels are not for venting about your manager. The skip-level is your manager’s manager. They will protect their direct report by default, and any complaint that lacks a specific action you’ve taken to address it first will be filed under “this person can’t handle their working relationships.”
If you genuinely need to raise something about your manager, frame it as a question about expectations: “I want to make sure I’m reading the priorities correctly. Here’s how I understand them. Is that right?” That gets you intel without burning the relationship.