Skip Level Meetings: Agenda, Questions, and Ground Rules

Bundle Performance: first demos in December

Bundle Performance turns every goal, check-in and review into a next step, and gives people the training to take it.

Get a demo

A skip level meeting gives a senior leader an honest read on what's happening two layers down. Run it with a clear agenda, specific questions, and ground rules that protect the manager in the middle, and it becomes your best early warning for manager skill gaps. This guide gives you a copyable agenda template, 20 questions for leaders, 6 for employees, and a way to turn what you hear into training that changes the next review.

What Is a Skip Level Meeting?

A skip level meeting is a conversation between a leader and an employee who reports to one of that leader's direct reports, without the middle manager present. Its purpose is to give the leader unfiltered insight into how work, culture, and management feel on the ground, and to give the employee visibility and access they wouldn't otherwise get.

It isn't a one-on-one. A one-on-one belongs to the manager and the employee and runs weekly or every other week. A skip level runs once or twice a year and exists to hear what the normal chain never carries up.

The "skip" is the point and the risk at the same time. You're deliberately bypassing a layer, which is what makes the meeting valuable and what makes it easy to mishandle.

Why Skip Level Meetings Matter

Information degrades as it moves up an org chart. Every layer summarizes, softens, and filters, usually with good intentions. Skip levels restore the sharp edges.

Most employees have no other formal channel upward. Gallup's 2023 workforce panel found that less than half of U.S. employees (42%) report having the opportunity to formally provide feedback to their manager. A skip level is one of the few structured places that feedback can surface.

It also catches problems before they become exits. In a Gallup survey of people who had voluntarily left a job, 45% said neither their manager nor another leader proactively discussed their job satisfaction, performance, or future with the organization in the three months before they left (published July 2024). When three people on the same team describe the same pattern in a skip level, you've found a development need months before an exit interview would have.

Skip Level Meeting Agenda Template You Can Copy

Use this template for every skip level meeting. It runs about 45 minutes, and the last block is the one most leaders skip. Copy it into your notes before the meeting.

  • Meeting: [Leader] with [Employee], who reports to [Manager]
  • Manager told: [Date]. Purpose and confidentiality explained.
  • 1. Frame (3 minutes): Why we're meeting. "Themes go back to your manager. Names and quotes don't, unless you ask me to share them."
  • 2. Work and obstacles (10 minutes): Two questions from the work list below. Note every obstacle in their words.
  • 3. The team (10 minutes): Two questions about how decisions and problems move through the team.
  • 4. Growth (10 minutes): One or two questions about development and what support they get.
  • 5. Open floor (5 minutes): "What should I have asked that I didn't?"
  • 6. Commitments (5 minutes): What I'll do, by when, and when we'll meet again.
  • After the meeting: Themes for the manager (no names). Issues I own. The skill pattern I heard (feedback, coaching, priorities, difficult conversations, development). Follow-up note to the employee by [date]. Next skip level on [date].

How to Run Each Part of the Agenda

Each block has one job. Keep to the times, because longer meetings drift into small talk or venting.

1. Set the frame

Say why you're meeting, what happens with what you hear, and that their manager knows. Skip this and the employee spends ten minutes working out whether they're in trouble.

2. Ask about the work and what gets in the way

Obstacles are where the organizational insight lives: a blocked approval, a tool nobody maintains, a team that never responds. These never reach you through normal channels.

3. Ask how the team works

Listen for how decisions get made and how often they mention their peers. You'll learn whether the team works as a team or as individuals reporting to the same person.

4. Ask about their growth

Employees rarely raise development themselves. This block is the one most likely to surface a manager development gap without anyone criticizing the manager.

5. Open the floor and commit

Ask what you didn't ask, then say what you'll do and when you'll meet again. A skip level with no visible follow-through is worse than none, because it proves speaking up changes nothing.

Skip Level Meeting Ground Rules

Set the rules before the first meeting and say them out loud at the start. Without them, a first skip level goes one of two ways: the employee spends 30 minutes saying everything is fine, or the leader walks out with complaints about a manager who wasn't in the room.

  • Tell the manager first. Skip levels should never surprise the person being skipped. Explain the purpose, the cadence, and what you will and won't share back. A manager who learns about skip levels from their team assumes the worst.
  • This isn't a performance review of the manager. Say so plainly. You're there to understand the work, the team, and the obstacles, not to build a case file.
  • Don't solve problems in the room. If you fix something the manager owns, you've taught the team to route around their manager. Note it and take it to the manager afterward.
  • Be clear about confidentiality. Themes go back to the manager. Names and verbatim quotes don't, unless the employee asks you to share them.
  • Keep it a conversation, not an interview. Share something real about your own priorities and pressures. People return candor; they don't return a clipboard.

Skip Level Meeting Questions That Get Real Answers

Pick five or six of these 20 questions per meeting, not the whole list. "How's everything going?" is a request to be reassured. The questions below are specific enough to answer and open enough to be honest.

Questions about the work

  • What's the most frustrating part of your week, and how long has it been that way?
  • If you could remove one process or approval, which one would it be?
  • What's something you're proud of that nobody outside the team knows about?
  • Where are you waiting on someone else more than you'd like?

Questions about the team

  • How do decisions get made on this team, and how do you find out about them?
  • When something goes wrong, what usually happens next?
  • Who on the team do you learn the most from, and why?
  • What's a disagreement the team had recently, and how did it resolve?

Questions about management and support

  • When was the last time you got feedback that changed how you work?
  • What does your manager do that you'd want every manager here to do?
  • What would make your one-on-ones more useful?
  • When you're stuck, who do you go to first?
  • Is there anything you need from your manager that's hard to ask for?

Questions about growth

  • Where do you want to be in two years, and does anyone here know that?
  • What skill would make the biggest difference in your work right now?
  • What's a stretch assignment you'd take on if someone asked?
  • What's the last thing you learned at work that you use every week?

Questions about the organization

  • What's a decision from leadership that made no sense from where you sit?
  • What do you think we're underestimating?
  • What would you fix first if you had my job for a month?

Only one cluster is about the manager, and it's framed around what the employee needs, not what the manager does wrong. That framing keeps the meeting honest without turning it into a complaint session.

Questions to Ask in a Skip Level Meeting as an Employee

If you're the employee, come with two or three questions of your own. A skip level is your best chance to understand the bigger picture and to be known by someone who influences your growth. These work well:

  • What are the top priorities for our group over the next two quarters, and how does my team's work connect to them?
  • What do you see from your seat that my team might not see from ours?
  • What skills do the strongest people at my level have in common?
  • Is there a decision you're weighing where a view from the ground would help?
  • How do you prefer to hear about problems before they get big?
  • Based on what you've seen of my work, what should I keep doing or change?

Keep criticism of your manager specific and about the work. If something is seriously wrong, say so plainly and ask how the leader wants to handle it.

How Often to Hold Skip Level Meetings, by Company Size

Meet each employee once or twice a year, and spread the meetings so you hold a few every month. The model changes with headcount.

  • Small companies (under 100 employees): The CEO or founder is often the skip level. Meet every employee at least twice a year. Everyone knows everyone, so confidentiality takes more care: share a theme only when more than one person raised it.
  • Small to mid-sized companies (100 to 500 employees): Directors and VPs run skip levels for the teams under their managers on a quarterly rotation. Managers at this size were often promoted fast and trained late, so skip levels pay off most here. HR should collect themes across leaders, without names, to spot patterns.
  • Large companies (over 500 employees): No leader can see everyone. Hold individual skip levels with a sample of each team, plus group sessions of five to eight people. HR aggregates themes across departments, so a gap that shows up in ten teams gets one program instead of ten separate conversations.

What to Do After the Meeting

The value is created in the 48 hours after the meeting, not in the room.

  • Debrief the manager within a week. Share themes, never attributions. "Two people mentioned that priorities shift without explanation" is useful. "Sarah said you change your mind constantly" is a betrayal.
  • Separate organizational issues from manager issues. A broken approval chain is yours to fix. A one-on-one cadence that has slipped is the manager's, and your job is to raise it, not fix it.
  • Log patterns across teams. One team mentioning unclear priorities is a manager conversation. Four teams mentioning it is a leadership problem, and it's yours.
  • Close the loop with the employee. Even a one-line note ("I raised the approval issue, here's what's happening") proves the conversation mattered.

Turn What You Hear Into Training

Every recurring skip level theme points to a skill the manager is missing, and each skill shows up later as a performance result: a vague review, a stalled goal, a resignation nobody saw coming. Name the skill, train it, and check it at the next conversation. Here are the five themes leaders hear most, with the skill behind each.

  • "Feedback is rare or vague." The skill is specific, behavior-based feedback. The manager practices real conversations from their own team with a trainer playing the employee, and redoes them until the feedback names the behavior and its impact. The check: at the next review, do the manager's written reviews cite examples the employee has already heard?
  • "Our one-on-ones are status updates, or they get cancelled." The skill is coaching. The manager practices asking open questions and holding back the answer, using a structured one-on-one meeting template. The check: at the next check-in, do goals show progress the employee owns?
  • "Priorities change without explanation." The skill is planning and explaining priorities. The manager practices turning a leadership decision into a two-minute explanation of the what and the why. The check: at the next skip level, can team members name the same top three priorities?
  • "Problems sit until the review." The skill is the difficult conversation. The manager rehearses the conversation they've been avoiding until they can open it in one sentence. The check: underperformance shows up in a check-in, with a written next step, weeks before it shows up in a review.
  • "Nobody knows where I want to go." The skill is the development conversation. The manager practices a career conversation and writes the result into an individual development plan. The check: every direct report has a development goal that gets reviewed at the next check-in.

At Bundle, this is the work of 1:1 Training: live, 90-minute sessions with an expert trainer on a structured lesson plan personalized by role, level, and industry, typically 6 to 8 sessions per person. Peer Reinforcement adds group sessions where managers practice together and build shared language. Many of the gaps skip levels uncover sit with managers in their first year, which is why new manager training is often the first program a skip level points to. For a broader map of the skills to build, see the 12 skills every manager training program needs.

Common Skip Level Meeting Mistakes

Running them only when something is wrong. If skip levels appear only in a crisis, employees learn that an invitation means trouble. Hold them on a steady cadence, regardless of how things seem.

Promising what you can't deliver. Leaders commit to fixes in the room, then get back to their calendar and forget. Every unkept promise costs you the next honest answer.

Only meeting the vocal people. The employees who volunteer are rarely the ones with the most useful perspective. Rotate through everyone. For a different angle on the people you're most at risk of losing, pair skip levels with stay interview questions.

Skipping the manager debrief. A manager who hears nothing after a skip level fills the silence with worst-case assumptions. The debrief is where the meeting turns into development.

Skip Levels Are Only Half the Job

The common view is that a skip level meeting is a listening exercise. That's right, as far as it goes. Listening is the hard habit to start, and most leaders never do.

What it misses is that listening changes nothing on its own. If a leader hears the same three themes from every team, mentions them to the managers, and the next round sounds identical, the meeting has become a checked box. The employee experienced a vent. The manager experienced a critique. Nobody got better at anything.

Treat each skip level as the start of a development plan for the manager. The theme names the skill. Training builds it. The next skip level, check-in, or review confirms it held.

Skip Level Meeting FAQ

What is the purpose of a skip level meeting? It gives a senior leader direct insight into how work and management feel two layers down, and gives employees access to leadership. Used well, it also shows where managers need development before the problem appears in reviews or resignations.

How often should you hold skip level meetings? Once or twice a year with each employee works for most leaders. More often crowds the manager's relationship with their team; less often makes the meetings feel like events instead of a rhythm.

Should the manager know what was discussed? Yes, at the level of themes. Tell the employee that at the start. Verbatim comments and names stay with you unless the employee asks you to share them.

What if an employee raises a serious concern about their manager? Listen fully, thank them, and don't react in the room. If it's a conduct issue, follow your HR process. If it's a skill or style issue, it becomes a development conversation with the manager, without attribution.

Can skip level meetings be done in groups? Yes, and group skip levels surface team dynamics well. People say less in groups, though, so use them alongside individual meetings, not instead of them.

Hold the Meeting, Then Build the Skill

A skip level tells you where your managers need help. Bundle's 1:1 Training gives each manager a live, expert trainer to build the skills your skip levels uncover. See how Bundle's manager training works.

Continue reading

Our newsletter

Sign up for our newsletter

Explore our library of webinars, ebooks, articles, and more from our team of experts.