Skip-Level Meeting Questions: 25 to Ask (and How to Run Them)

What a skip-level meeting is actually for

A skip-level is a 1:1 between you and someone who reports to one of your direct reports. You're skipping a level of the org chart — hence the name. Because you're skipping a level, the meeting has a different job than a regular 1:1. Four jobs, really:

• Ground truth. Information degrades as it moves up. By the time a problem reaches you through two layers of status updates, it's been rounded off, softened, and summarized. Skip-levels are where you hear the un-rounded version.
• Early warning. Burnout, brewing conflict, a manager who's struggling — these show up in skip-level conversations months before they show up in metrics or resignation letters.
• Visibility both ways. People two levels down get to be a person to you instead of a name on an org chart, and they hear strategy from the source instead of through a game of telephone.
• Calibration. You find out how well your priorities survived the trip down through your managers. If nobody two levels down can name the team's top priority, you just learned something important — about your communication, not theirs.

Just as important is what skip-levels are not: a performance review, a place to assign work, or a secret back-channel around the manager in the middle. The moment they become any of those, they stop working — and word travels fast.

Don't undermine the manager in the middle

The biggest risk of skip-levels isn't awkward silence — it's accidentally kneecapping the manager you're skipping. Everything about how you run these meetings should signal that you're supporting that manager, not auditing them.

• Announce them through the manager. Before any invite goes out, tell your direct report: "I'm starting skip-levels with everyone on your team. Here's roughly what I'll ask, and I'll share themes back with you — never who said what." No surprises.
• Never assign work or change priorities in a skip-level. If someone asks "should we be doing X?", the answer is "good question — raise it with your manager, and tell me if it stalls." You redirect; you don't decide.
• Don't fish for dirt. "How's Sarah doing as a manager?" puts the person in an impossible spot. Ask about support instead: "Is there anything the team needs that it isn't getting?" If there's a real manager problem, it will surface without you dredging for it.

When someone does bring a complaint about their manager — eventually someone will — resist the urge to fix it live. A script that works: "That sounds genuinely frustrating. Have you told them directly? I'm not going to act on one conversation, but I do pay attention to patterns, and I'm glad you told me." That's honest, it protects the person, and it doesn't turn a single data point into a verdict.

25 skip-level questions, grouped by what you're listening for

Don't bring all 25 — pick five to seven and let the conversation wander. Notice these are deliberately different from regular one-on-one meeting questions: you're not managing this person's work, so the questions aim at the system around them, not their task list.

Openers that don't feel like an interrogation. Start with genuine curiosity about them, not the org.

• What are you working on right now that you're actually excited about?
• What took you the longest to figure out about how this team really works?
• What do you wish I understood better about your day-to-day?
• What's the best part of a typical week for you — and the part you dread?
• If you had my job for a week, what's the first thing you'd dig into?

How the work actually happens. This is where the un-rounded truth lives.

• What's the most frustrating part of getting your work done here?
• Where do you lose the most time — tools, process, or waiting on other people?
• What's something we do purely because we've always done it?
• Tell me about a recent decision that took way longer than it should have. What happened?
• What do other teams complain about when they work with us?

Team health and early warnings. Listen for hesitation as much as content — the pauses are data. If several people describe the workload the same worrying way, cross-check what you're hearing against the signs of employee burnout.

• How's the workload right now — sustainable, tight, or underwater?
• When people on the team disagree with a decision, do they say so out loud?
• Who on the team is doing great work that nobody notices?
• Is there anything people have stopped raising because nothing changed the last time they raised it?
• What would make a good person here quietly start looking elsewhere?

The org, strategy, and communication. You're testing how well information travels in both directions.

• What's a recent org decision that didn't make sense from where you sit?
• Can you name our top two priorities this quarter? (If not, that's my problem, not yours.)
• What information do you get too late — or not at all?
• What do you think leadership — me included — is getting wrong right now?
• If you could change one thing about how the org runs, what would it be?

Growth and the future. Career topics land differently coming from two levels up — use that.

• What skill do you want to build this year, and are you actually getting chances to build it?
• Where do you want to be in two years — and does anyone here know that?
• What's the most useful piece of feedback you've gotten recently?
• Is there a project outside your team you'd love a crack at?
• What would make this a place you stay for the next few years?

Cadence and logistics that actually scale

Skip-level frequency is a math problem before it's a philosophy problem. Five managers with six reports each means thirty people. Monthly skip-levels would be thirty extra meetings a month — you'd do nothing else. What works in practice:

• Quarterly per person if your skip-level population is under about 15 people.
• Twice a year per person for 15-40 people, plus an occasional group skip-level — one team, no manager, 45 minutes — to keep a pulse between rounds.
• 30 minutes is right for a recurring skip-level. Make the first one with each person 45 — you need the extra time to establish that this is routine, not a sign something's wrong.
• Rotate deliberately. Left to default, you'll end up meeting the senior, the confident, and the loud. Keep a simple roster so the quiet mid-level engineer gets the same airtime as the staff engineer who books time with you anyway.

The invite matters more than you'd think. A bare calendar invite from two levels up reads as "am I in trouble?" Add one line of context: "I do these with everyone a couple of times a year — nothing's wrong, no prep needed. I mostly want to hear how things look from where you sit." And keep this rhythm separate in your head from 1:1s with your own direct reports, which run on a much tighter loop — here's how often one-on-ones should happen if you're calibrating both.

What to do with what you hear

A skip-level where nothing happens afterward is worse than no skip-level — you've asked people to be honest and then demonstrated that honesty changes nothing. Question 14 on the list exists because this failure mode is exactly that common.

• Sort everything into three buckets: one-off (park it), pattern (act on the system), urgent (act now — ethics, safety, harassment). Only the third bucket justifies acting on a single conversation, and if something lands there, tell the person in the room that you'll have to act on it.
• Aggregate before you relay. Wait until you've done several skip-levels, then bring your manager themes: "Three people independently mentioned that decisions stall in the platform review." Themes are actionable; verbatim quotes are betrayals.
• Close the loop publicly. When something changes because of skip-levels, say so wherever the team gathers: "A few of you flagged the deploy process — here's what's changing." Even "we looked at it, and here's why we're not changing it" builds more trust than silence.
• Track what you were told. If someone mentions wanting a stretch project and six months later you've done nothing with that, your next skip-level will be thirty minutes of polite nothing. Keep light notes per person — a tool like Teammons keeps running notes and follow-up action items attached to each person, so nothing you heard quietly evaporates.