Skip Level Meetings: 45 Questions + Agenda

A calendar invite lands from your boss's boss. Thirty minutes, no agenda, subject line just your first name. You look at it a second longer than you'd like to admit, then message a teammate: "Did you get one of these too?"

That flicker of dread is the whole problem with the skip level meeting. Run well, it's the highest-signal half hour on a senior leader's calendar. Run badly, it's a rumor generator. Here's the honest version: what it is, why it feels weird from both sides, how each side preps, 45 questions worth stealing, and how leaders wreck it.

What a skip level meeting actually is

The skip level meeting meaning sits right in the name: a senior leader talks directly with someone two rungs below, skipping the manager in between. Your director meets your engineer, and that manager's absence is the design.

Companies run them because information degrades as it climbs. Every management layer is a compression algorithm, summarizing and smoothing, until a real frustration arrives upstairs as "the team's a bit stretched." Gallup has pegged trust in senior leadership at about one in five employees for years, and much of that gap is plain distance.

The senior leader owns this one. Quarterly is the common cadence, twice a year a defensible floor, monthly worth it during a reorg. Group versions of four to six spot patterns fast, but nobody says the hard thing in front of peers.

The weekly conversation a manager has with their own reports is a different animal, and we've published a full 1:1 meeting template for managers on it. Treating a skip level like a borrowed 1:1 is how most go wrong.

Why the invite makes everyone nervous

Now the part HR guides skip. From the employee's chair: Is this a loyalty test? Am I being asked to inform on my boss? Does the honest answer come back with my name attached? And underneath it — whatever I say, I still have a 1:1 with my actual manager on Thursday.

From the middle manager's chair it's no better. My boss is meeting my team without me. Is this an audit? Managers who feel investigated pre-brief the team and coach people on messaging — not villainy, just a normal reaction to exclusion.

Both anxieties share one root: ambiguity about what happens to the information. So both have the same fix, and it isn't a warmer tone.

The sentence that defuses most of it: "I do these with everyone every quarter. I'm listening for patterns, not complaints. Nothing gets repeated with your name on it — if something needs fixing, I'll raise it as a theme, and I'll tell you first."

Preparing as the senior leader

Tell the middle manager first, properly. Not a Slack message twenty minutes ahead. Explain what you're doing, why, who's on the list, and what you'll share — then ask what they'd like probed.

Do your homework. Know what they own and one specific thing you can name. Nothing says "formality" faster than asking what team someone's on.

Bring three questions, not twelve. Three openers plus real follow-ups beat a survey read aloud. Send them ahead and quiet people give you far more.

Settle your confidentiality rule first. "Themes, not names" holds up. Know the exceptions — harassment, safety, and anything legal go to HR regardless, so don't promise secrecy you can't honor.

Preparing as the employee

If you're on the receiving end, you have more leverage than you think. Start by asking what it's for: "Happy to — anything specific you'd like me ready to discuss?" A leader running a quarterly round will say so.

Bring one thing that's working and one that's genuinely stuck. The first is calibration, not flattery; leaders who only hear problems start discounting all of it. The second is your opportunity — half an hour with someone who can unstick another department in one message.

And yes, you can talk about your manager — behavior and effects, not character. "I don't hear about priority changes until after they've happened, and it cost me a week last month" is specific and hard to weaponize. "She's disorganized" just gets dismissed or repeated.

One honest caution. Confidentiality here is a norm, not a guarantee. A few leaders leak by accident, acting so specifically that everyone reverse-engineers the source. Before you share, ask whether you'd be fine if it came back with your name on it.

45 skip level meeting questions, grouped by what you're after

Pick three, not thirty. Open with the work, move to friction, save the manager for the middle. Follow-ups beat openers — "what happened next?" is where the information lives.

Group 1 — Understanding the work

Low-risk openers that buy credibility for harder ground.

1. Walk me through what you actually spent last week on.
2. Which part of your job would surprise me most?
3. What does "done" look like for what you're on now?
4. Who outside this team do you depend on?
5. What context do you have that I probably don't?
6. How would you explain this team's job to a new hire?
7. What's the most repetitive thing you still do by hand?
8. Which project would you stop if nobody noticed?

Group 2 — Testing whether the strategy landed

Vague answers here are a finding about you.

1. In your own words, what are we trying to win at this year?
2. Where did you first hear our priorities — doc, meeting, or grapevine?
3. Which priority feels real day-to-day, and which feels like a slide?
4. What do you think leadership cares about most now?
5. Is there a decision from last quarter you still don't get?
6. What would you struggle to explain to a customer?
7. If we're wrong strategically, what's the likeliest candidate?

Group 3 — Surfacing blockers and friction

Invisible from your seat, fixable from it.

1. What last took three times longer than it should have?
2. Which approval or handoff slows you down most?
3. What tool or access do you keep working around?
4. Where do two teams keep tripping over each other?
5. What problem gets raised repeatedly and never fixed?
6. If you could delete one recurring meeting, which one?
7. What do people complain about in DMs, never in meetings?
8. What would let you ship two weeks earlier?

Group 4 — Manager effectiveness, handled carefully

Mechanics only. Never ask anyone to rate their boss.

1. Do priorities reach you clearly, or pieced together?
2. When you raise a problem upward, what happens next?
3. How much notice do you get when priorities change?
4. What feedback have you had this month, and was it usable?
5. Where does your team move fastest, and where does it stall?
6. What does your manager do that others should copy?
7. If your manager vanished for a month, what breaks first?
8. Is anything about how this team runs hard to say?

Group 5 — Career growth and retention

1. What would make you turn down a recruiter outright?
2. What skill are you building on your own time that we ignore?
3. Who here has taught you the most, and what?
4. What's the next role you want, and does it exist here?
5. What would have to be true for you to still be here in two years?
6. Which of your work belongs in a portfolio?

Group 6 — Culture and candor

Save for late. In minute two you get a press release.

1. What's normal here that would look strange elsewhere?
2. When did someone last openly disagree with a senior person?
3. What do we say we value that our budgets don't?
4. Who does great work that leadership never sees?
5. What rule here do people quietly ignore?
6. What would you change about how information moves here?
7. What question should I be asking that I'm not?
8. What's the one thing you hope I actually fix?

These aren't warm-ups for a standing meeting — different genre, different rules, covered in our check-in questions for team meetings.

A thirty-minute structure that isn't an interrogation

Half an hour is right: past the polite layer, short of anyone dreading it.

Skip level agenda — 30 minutes

0–3 min Frame it. Why you're doing this, who else you're meeting, what happens to what they say.

3–8 min Them, not the org. What they own, what's gone well. Low stakes on purpose.

8–20 min The real block. Two or three prepared questions plus follow-ups. Let silence work — the second answer is the honest one.

20–26 min Their agenda. "What did you want to raise that I haven't asked?" Then stop talking.

26–30 min Close out loud. Say back what you heard, name what you'll act on, confirm what goes upward.

Priya is a VP; Sam is a support engineer two levels below her.

Filled example — Priya × Sam

Working The new triage rota. Sam's escalation queue went from roughly 40 open tickets to 12 since June.

Stuck Refunds over $500 need a director sign-off taking two to three days. Customers wait, Sam absorbs the anger, and he assumed it was fixed policy.

Strategy Asked what we're trying to win at this year. Sam names last year's goal — Priya's problem, not his.

Mechanics Priorities arrive clearly; his manager shields the team from planning churn.

Commits (1) Find out whether the $500 threshold is real policy, by Friday. (2) Rewrite how goals get communicated. (3) Credit the rota to Sam's manager, by name.

Note what's missing: no ratings, no gossip, no performance talk. Two commitments, one thing Priya learned about herself.

Five ways leaders wreck it

1. Performance-managing someone else's report. Critical feedback on their work takes a job that belongs to their manager, with a fraction of the context. Praise is the only feedback safe to give directly.

2. Blindsiding the middle manager. The most common failure. A manager who finds out afterward spends a month wondering what was said — a month of your bench quietly less effective.

3. Letting it become a status meeting. Spend twenty-five minutes on an update you could have read in a doc and you've burned the one meeting built to surface what isn't in the doc.

4. Overpromising in the room. Someone raises an infuriating process and you hear yourself say "let me get that killed." Six weeks later it's still there. Say "I'll find out by Friday" instead — then say something on Friday, even if it's no.

5. Doing it once. A one-off round after a bad engagement survey reads exactly like what it is. Quarterly and unremarkable beats intense and sporadic.

The test to run before you speak: "Would I be fine if this person repeated my exact sentence to their manager tonight?" If not, don't say it. That filter blocks most of the ways these go wrong.

Closing the loop without breaking trust

The debrief with the middle manager decides whether you get honest answers again.

Report themes, in aggregate, across the whole round. "Across five conversations, two things kept coming up: nobody can tell which priority wins when they conflict, and refund approvals are costing us days." That protects people structurally, not through your discretion. If you've met only one person, wait — a theme from one conversation is a quote in a costume.

Three rules keep it clean. Praise gets attributed by name, always. Criticism never does. And if something is specific enough that the manager could guess the source, ask the employee first.

Then there's follow-through, where most of this dies. Two commitments per conversation across six people is a list you won't remember, so write each down with an owner and a date the moment the call ends — which is what our guide to writing action items that get done is really about. The work that follows lands in your staff meetings and 1:1s, and that's where an AI notetaker earns its keep: Laxis transcribes Zoom, Meet, and Teams calls and extracts action items with owners, free for 300 minutes a month.

This is one meeting you probably shouldn't record. Candor and a recording indicator don't coexist. Take sparse notes, or none, and write your summary in the five minutes afterward. Formal write-ups are a different craft — see how to write meeting minutes.

Last step: report back to the people you met. A short note a few weeks later — what I heard, what changed, and what I looked at and chose not to change, and why. That last clause buys the next round of honesty.

Keep the promises you make in the room

Laxis records, transcribes, and summarizes your team meetings and 1:1s across Zoom, Meet, and Teams, then pulls out action items with owners. Free plan, 300 minutes a month, 100+ languages.

Try Laxis Free

The bottom line

The surprising thing about running these is that good ones almost never produce a scandal. What you get is a slow pile of small, boring, fixable friction — a form nobody owns, an approval threshold set in 2019, a goal three people can't recite. None of it reaches you otherwise, because none of it is dramatic enough to escalate.

Frequently asked questions

What is a skip level meeting?

A skip level meeting is a conversation between a senior leader and someone two levels below them, with that employee's direct manager not in the room. The leader skips a rung of the hierarchy to hear how the work actually feels on the ground.

How often should skip level meetings happen?

Quarterly is the most common rhythm, with twice a year a realistic floor for a leader running several teams. Monthly earns its place during a reorg. Predictability matters more than frequency — an unscheduled skip level reads as an investigation.

What should you ask in a skip level meeting?

Ask about the work, not about people. Good openers cover what someone actually spent the week on, which priorities feel real day to day, and what routinely takes far longer than it should. Never ask anyone to rate their boss.

Is a skip level meeting a bad sign?

Usually not. In most companies it's a scheduled listening habit that runs across a whole team, not a signal about you. It's worth a second thought only when it appears suddenly or targets one person. If you're unsure, ask what prompted it.

Should the middle manager know about a skip level meeting?

Yes, always, and before the invite goes out. Tell them what you're doing, why, who you're meeting, and what you will and won't share afterward. Skipping that step is the fastest way to make a manager feel investigated and start coaching their team.

What should you never do in a skip level meeting?

Never give performance feedback, assign work, or reverse a decision belonging to the manager you skipped. Never ask anyone to grade their boss, and never repeat a comment with a name attached. Each turns a listening conversation into a power move.