Skip-Level Meetings: How to Run Them and What to Ask (Questions, Agenda & Template) 2026

Few calendar invites produce as much quiet panic as "30 min with your manager's manager". Employees wonder what they did wrong. Middle managers wonder what will be said about them. And the senior leader who sent the invite mostly wonders why every answer sounds suspiciously polished.

None of that is inevitable. A skip-level meeting, done well, is one of the highest-leverage conversations in a leader's calendar: it surfaces problems while they are still cheap to fix, shows employees that their work is visible two levels up, and gives leaders a picture of the organization that no dashboard or status report can provide.

This guide covers the whole format: what a skip-level meeting is, how to set one up as a leader without triggering alarm bells, how to prepare as an employee, question catalogs for both sides, a copy-paste agenda template, and how to capture what was said without making the conversation feel like a deposition.

⚠️ This article was independently compiled based on publicly available information and user feedback as of August 2026.

Table of Contents

1. What is a skip-level meeting?
2. Why skip-level meetings matter
3. How to run skip-level meetings as a leader: a checklist
4. How to prepare as an employee: example answers
5. Skip-level meeting questions that work
6. Copy-paste skip-level meeting agenda template
7. The notes: documenting without chilling the conversation
8. Common skip-level meeting mistakes
9. FAQ
10. Conclusion

What is a skip-level meeting?

A skip-level meeting is a conversation between a senior leader and an employee who reports to one of that leader's direct reports, without the middle manager in the room. The leader "skips a level" of the org chart: a director meets an engineer who reports to one of her engineering managers, a VP of Sales meets an account executive two levels down.

The purpose is not to bypass the middle manager or to audit them. It is to give the leader unfiltered signal about how work actually feels on the ground, and to give employees direct access to the person shaping decisions that affect them. In healthy organizations, skip-levels and regular 1:1s complement each other rather than compete:

Two formats are common: 1:1 skip-levels (one leader, one employee, the default for candid conversation) and group skip-levels (one leader, a whole team without its manager, useful in larger orgs where meeting everyone individually is unrealistic). This guide focuses on the 1:1 format; most of it transfers directly to groups.

Why skip-level meetings matter

The case for skip-levels is often made vaguely, "stay connected to the front line", so it is worth being concrete about what they actually buy each side.

For the leader:

• Early warnings. Attrition risks, brewing conflicts, and process breakdowns show up in skip-level conversations one or two quarters before they show up in metrics or exit interviews.
• Calibration. Hearing how strategy lands two levels down tells you whether your communication survives translation. If nobody can explain why the current priority matters, that is your finding.
• A read on management quality. Not by asking "how is your manager?", which puts the employee in an impossible spot, but by noticing patterns across many conversations: which teams feel informed, which feel stuck.

For the employee:

• Visibility. Your work and your thinking become known one level above your manager, which is where staffing and promotion conversations actually happen.
• Context. You hear the reasoning behind decisions first-hand instead of via two rounds of paraphrase.
• A channel. If something systemic is broken, tooling, process, workload, you can raise it where budget and authority exist.

For the middle manager, counterintuitively, a well-run skip-level program is also a win: their asks for headcount or tooling get validated by their own team's voice, and "my manager already flagged this" is the most common sentence in a good skip-level.

How to run skip-level meetings as a leader: a checklist

Skip-levels live or die on trust, and trust is mostly built in the setup, before the first question is asked.

• Tell the middle managers first. Announce the program to your managers before any invite goes out, and frame it accurately: this is how you stay informed, not how you check up on them. A manager who learns about skip-levels from their confused report will treat the whole program as a threat.
• State the purpose in the invite. Two or three sentences: why you do skip-levels, what you will ask, what happens with the notes. An unexplained invite from two levels up reads as "am I in trouble?" to almost everyone.
• Make it a routine, not an event. A quarterly or twice-yearly rhythm, covering everyone over time, removes the "why me?" anxiety. A one-off skip-level with a single person is a signal; a rotation is a system.
• Keep it to 30 to 45 minutes. Long enough for depth, short enough that neither side needs to perform.
• Let the employee talk. Your target share of talking time is 20 to 30 percent. You are there to collect signal, not to broadcast; that is what the all-hands is for.
• Never make it an evaluation of the manager. If you ask "how is your manager doing?", you have converted your listening channel into a loyalty test. Ask about the work, the blockers, and the flow of information instead; management quality emerges from patterns, not from testimony.
• Close the loop. The fastest way to kill a skip-level program is to hear the same problem three times and change nothing. Track themes, act on at least the cheap fixes, and tell people what changed because of these conversations.

How to prepare as an employee: example answers

If a skip-level lands in your calendar, the single most important reframe is: this is an opportunity, not an audit. Leaders run skip-levels to find out what is actually going on. The employees who benefit most treat the slot with the same seriousness as a project review.

Prepare three things in advance: one concrete thing that is going well, one friction point you can describe factually, and one question you genuinely want answered. Some phrasings you can adapt:

• "How are things going?" Answer with substance, not weather-talk: "Genuinely good on the project side. The migration shipped two weeks early. The one thing wearing us down is the release process, we lose about a day per sprint to manual steps."
• "What would you change if you could?" Be specific and systemic, not personal: "The handoff between design and engineering. Specs arrive after estimates are locked, so we re-plan every sprint. A shared definition-of-ready would fix most of it."
• "Is there anything I should know?" This is your channel, use it factually: "Two senior people on the neighboring team are visibly burning out. It is not my call, but you would want to know before Q4 planning."
• What not to do: do not use the meeting to torpedo your manager, relitigate a performance rating, or negotiate compensation. All three make the leader defensive and mark you as someone who mistakes access for leverage. If you have a genuine conflict with your manager, name the topic and ask for the right forum instead.

Write your three points down before the meeting. Thirty minutes with a senior leader disappears faster than any meeting you know.

Skip-level meeting questions that work

Good skip-level questions are concrete, answerable from the employee's own experience, and free of traps. A catalog for both sides:

For leaders: understanding the work

• What are you working on right now, and what part of it would you be excited to show me?
• Where does time disappear in your week that outsiders would not guess?
• If you could delete one process or meeting tomorrow, which one and why?

For leaders: information flow and strategy

• How did you hear about the last big decision that affected your team? Did the reasoning survive the trip?
• What is something your team knows that you suspect leadership does not?
• What are we, as a company, pretending not to see?

For leaders: growth and retention

• What would need to be true for you to still be excited about this job in a year?
• Whose work on your team deserves more visibility than it gets?
• What skill do you want to build that your current work does not exercise?

For employees: questions to ask your skip-level leader

• What is the biggest bet the department is making this year, and how does my team's work feed it?
• What do you see as the difference between people who grow fast here and people who plateau?
• What is one thing you wish teams at my level did differently?
• How do you personally prefer to receive concerns: directly, via my manager, or another route?

The rule that separates a good skip-level from a stiff one: fewer questions, real follow-ups. One thread pulled properly, "you said the release process eats a day per sprint, walk me through it", beats ten questions answered at survey depth.

Copy-paste skip-level meeting agenda template

Paste this into your calendar invite or notes tool. It fits a 30 to 45 minute 1:1 skip-level; for group formats, extend the middle blocks.

# Skip-level: [Leader] x [Employee] – [Date]
Cadence: [quarterly / half-yearly] · Middle manager informed: [yes]

## Framing (2 min)
- Purpose: unfiltered context, not evaluation
- Notes: what is captured, who sees them

## Their world (15 min)
- Current work, and what they are proud of:
- Where time and energy leak:
- One thing they would change:

## Information flow (10 min)
- How decisions and strategy land at their level:
- What leadership should know but might not:

## Their questions for me (10 min)
- (employee's questions, prepared in advance)

## Close (3 min)
- Themes I heard:
- Follow-ups with owners and dates:
- What I will share back, and with whom

The last block is the trust engine of the whole format. Follow-ups with owners and dates, plus clarity about what gets shared with the middle manager, are what make the next skip-level in this rotation easier instead of harder.

The notes: documenting without chilling the conversation

Skip-levels have a documentation paradox. The whole value of the format lives in patterns across many conversations, which team names the same blocker, which themes repeat quarter over quarter, so notes matter more than in almost any other meeting type. But visible note-taking is exactly what makes a nervous employee retreat to safe answers. A leader typing every time the conversation touches something sensitive is running a transcription of a deposition, not a conversation.

This is the gap a real-time AI meeting assistant closes. SuperIntern is a bot-free desktop app that captures the conversation straight from your computer's audio. No bot joins the call, which matters twice here: a "Notetaker has joined" banner is precisely the deposition signal you are trying to avoid, and skip-levels happen everywhere, Zoom one week, Microsoft Teams the next, a walk-and-talk with a phone on the table after that. Because SuperIntern listens at the device level, the workflow is identical across all of them.

For skip-levels specifically:

• You keep eye contact during the sensitive parts. The notes build themselves live, so the moment someone finally says the honest thing is not the moment you look down to type.
• Your template fills itself in. With AI Canvas you describe the structure once, for example: "This is a skip-level conversation. Capture what is going well, friction points, information-flow issues, the employee's questions, and follow-ups with owners." Every conversation in the rotation fills the same form, which is what makes themes comparable across ten conversations.
• Patterns become searchable. When the third person this quarter mentions the release process, the earlier mentions are in your notes, not in your fading memory. Post-meeting AI chat lets you ask across meetings: "what blockers came up in my skip-levels this quarter?"
• You control where the record lives. Skip-level notes belong in a private space where only you can see them, not in a shared team workspace. Nothing is passed on unless you actively share or export it, which is exactly the promise you made in the framing minute.

One thing is non-negotiable: transparency. Tell the employee at the start that an AI tool is taking notes, say what happens with them, and get their consent. Recording laws differ by country and, in the US, by state (one-party versus all-party consent), and beyond the legal detail, a covert recording in a trust-building meeting is self-defeating. Used openly, the tool sends the opposite signal: what gets captured is what was actually said, not one side's recollection of it.

Common skip-level meeting mistakes

• Springing it on people. An unexplained invite from two levels up costs a week of anxiety and buys you thirty minutes of rehearsed answers. Announce the program, then invite.
• Turning it into a manager tribunal. Asking reports to rate their manager poisons all three relationships. Ask about the work; patterns will tell you the rest.
• The leader talking 70 percent of the time. If you leave having delivered a vision speech, you collected nothing. That speech has a venue, and it is not this one.
• Collecting problems and fixing none. Three rounds of "thanks, great feedback" with no visible change teaches the org that skip-levels are theater. Fix the cheap things fast and say so.
• Breaking confidentiality casually. "Someone on your team told me..." travels back in minutes and ends honest input permanently. Share themes, never attributable quotes, and tell people that is the rule.
• Canceling when the calendar gets tight. Skip-levels are the first thing busy leaders drop and the clearest signal of what actually matters. A canceled skip-level says more than the meeting would have.

FAQ

Is a skip-level meeting a bad sign? Am I in trouble?

Almost never. Leaders run skip-levels to understand how the organization is doing, and a well-run program covers everyone in rotation. If the invite explains the purpose, take it at face value. Trouble arrives via your own manager and HR, not via a get-to-know-you slot with a director.

Should I tell my manager what was discussed?

Being open with your manager about the fact of the conversation is healthy, and a short "we talked about the roadmap and the release process" keeps trust intact in both directions. You are not obligated to reproduce it verbatim. Good leaders share themes back with the middle manager anyway, without attributing quotes.

How often should skip-level meetings happen?

Quarterly to twice a year per employee is the common range. Frequency matters less than regularity: a predictable rotation reads as a system, an ad-hoc invite reads as an alarm. Leaders with large orgs often mix 1:1 skip-levels for some levels with group skip-levels for others.

Who sets the agenda for a skip-level?

The leader sets the frame and shares it in advance; the employee should bring their own points and questions. The strongest format reserves a third of the time explicitly for the employee's questions to the leader.

What should I not say in a skip-level meeting?

Avoid three things: attacks on your manager (name a topic and ask for the right forum instead), compensation negotiation (wrong venue, wrong participant), and anything you would not want summarized as a theme. Factual friction points are welcome; venting rarely survives the trip up well.

Are skip-level notes confidential?

That is the leader's promise to make and keep: themes get shared, attributable quotes do not. If it is not addressed, ask directly, "how will what I say here be used?". A leader who cannot answer that cleanly has not designed their program yet.

Do skip-level meetings work remotely?

Yes, and remote orgs arguably need them more, since hallway signal does not exist. The mechanics are identical; the extra rule is to keep cameras on if you can, and to be even more explicit about note-taking and confidentiality, since remote employees cannot read the room's body language.

Conclusion

A skip-level meeting is a simple format with unforgiving mechanics. Announced properly, run as a rotation, built on real questions and a visible follow-up loop, it gives leaders their earliest warning system and employees their most direct channel. Set up carelessly, it produces rehearsed answers, nervous managers, and notes nobody acts on.

The difference is almost entirely process: tell managers first, explain the purpose, talk less than you listen, protect confidentiality, and close the loop visibly. And treat the record with the same care as the conversation: notes that capture what was actually said, in a template that makes ten conversations comparable, are what turn a pleasant chat into an early-warning system.

Try SuperIntern Free: no bot in your most sensitive conversations, live notes that follow your skip-level template, and a searchable record across every conversation in the rotation.