> ## Content Index
> Fetch the complete content index at: https://playbooksforleaders.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Skip-level meetings: what they are for and what to ask
- URL: https://playbooksforleaders.com/journal/skip-level-meetings/
- Published: 2026-11-20T07:15:00.000Z
- Updated: 2026-11-20T07:15:00.000Z
- Description: How to run a skip-level meeting without going around your managers: how often, what to ask and what to do with what you hear.
- Author: Will Rowan
- Tags: #journal, Team & People, #podcast, #infographic

## The short version

- In a skip-level meeting, you meet the people who report to your managers, without those managers in the room.
- Hold them at least every quarter, one at a time or in groups of up to 15.
- Before you start, tell the managers in between why you're doing it and what you'll do with what you hear.
- Never use one to check up on a manager or to do their job.
- Give your update first, then leave most of the time for their questions.

Playbooks for Leaders Podcast, Episode 9: Skip-Level Meetings

0:00

/1634.4

1×

## Contents

- [What is a skip-level meeting?](#what-is-a-skip-level-meeting)
- [What is a skip-level meeting not for?](#what-is-a-skip-level-meeting-not-for)
- [How often should you hold skip-level meetings?](#how-often-should-you-hold-skip-level-meetings)
- [How do you run a skip-level meeting?](#how-do-you-run-a-skip-level-meeting)
- [What should you ask in a skip-level meeting?](#what-should-you-ask-in-a-skip-level-meeting)
- [What do you do with what you hear?](#what-do-you-do-with-what-you-hear)
- [What if you're the manager being skipped?](#what-if-youre-the-manager-being-skipped)

Once your team has managers in it, you stop hearing directly from the people doing the work. Everything reaches you through someone else. A skip-level meeting is how you hear it first-hand, as long as you don't use it to go around the managers in between.

![Infographic on skip-level meetings. A leader in a white shirt meets a group of team members two levels down, while their manager, a man in a green jumper, waits outside the door. In the panels below, he talks with a team member in a blue jacket and recognises her work. He doesn't check up on her manager, passes back themes without names and leaves most of the time for questions.](https://playbooksforleaders.com/content/images/2026/11/skip-level-meetings-infographic.png)

A skip-level meeting is how you hear first-hand from the people doing the work, without going around their managers. How often to hold one, and what to ask.

## What is a skip-level meeting?

GitLab's handbook defines it as "a meeting during which a manager's manager meets directly with team members without the direct manager present" ([GitLab, Skip level meetings](https://handbook.gitlab.com/handbook/leadership/skip-levels/?ref=playbooksforleaders.com)). It's different from a [one-to-one](https://playbooksforleaders.com/journal/one-to-one-meetings/), which you hold with the people who report to you.

You get four things from it. You learn how your strategy sounds by the time it reaches the people doing the work. You find out what the team is proud of that nobody passed up. They get to ask you a question directly. And they see that the person two levels up knows their name.

## What is a skip-level meeting not for?

GitLab's handbook names two things it is not for. One is checking "on the performance of a manager by 'going around them'". The other is taking on priorities, career conversations or any other duty that belongs to the direct manager.

If you break either rule, the managers in between have good reason to stop trusting you, and their teams to stop trusting them. Tell each manager before the first skip-level what you're doing and why, and tell them what you'll pass back.

## How often should you hold skip-level meetings?

At least every quarter. GitLab sets that floor and leaves anything more often to the leader.

You can meet people one at a time or in groups. GitLab caps a group at 10 to 15, so that people take part. If your organisation is too big to meet everyone each quarter, GitLab's handbook says to meet a different group each quarter.

## How do you run a skip-level meeting?

1. Make the first one a conversation with no agenda. If you meet people one at a time, GitLab compares the first meeting to a coffee chat, there for you to get to know each other.
2. Before each later one, look up what the people attending have done recently, and open by saying so. They hear that their work reached you.
3. Give your update next: the strategy, what's changed and what the organisation is focused on this quarter.
4. Leave most of the time for their questions.

Don't worry about repeating yourself. GitLab's handbook says one of the commonest reactions managers have after a skip-level is "I thought everybody knew that!" It adds that you often have to say a thing several times, in several ways, before people take it in.

GitLab never records them, because it uses them to build trust with the team.

## What should you ask in a skip-level meeting?

Ask questions about the work and the organisation, never about their manager:

- What slows you down that I could fix?
- What have you heard about our strategy that doesn't make sense?
- What's the team proud of that I probably don't know about?
- What should I stop doing?
- If you were in my job for a week, what would you change first?

If the room goes quiet, [The room's gone quiet Playbook](https://playbooksforleaders.com/meetings-decisions/room-gone-quiet/) has two moves: ask the most naive question you can think of, or ask for the three worst ideas. The first gives people permission to say the obvious, and the second takes the pressure off being right.

## What do you do with what you hear?

Take themes back to the managers in between, without names. "Three people told me the approval process takes a week" lets the manager fix the process. "Priya told me you're slow to approve things" ends Priya's honesty, and possibly the manager's trust in you.

Fix the things that are yours to fix, and say so at the next skip-level. People keep raising problems when they see something happen. In the [Falling morale Playbook](https://playbooksforleaders.com/discovery-understanding/falling-morale/)'s words, "if people flag something and nothing visibly happens, the next round will flag nothing".

If someone raises conduct or the law, go to HR, and tell the person that you will.

## What if you're the manager being skipped?

Treat it as normal and tell your team it's normal. Ask your boss for the themes afterwards. Never ask your team what they said.

If the themes surprise you, take them to your own one-to-ones. Your team told your boss something they hadn't told you, and the question is why. If your own one-to-ones surface nothing, the Falling morale Playbook has a first move for that: stop them for a month, and ask people to meet each other weekly instead.

## FAQ

### Should the middle manager attend the skip-level meeting?

No. The meeting works because the manager isn't there. Tell them it's happening, why and what you'll pass back.

### Are skip-level meetings confidential?

Treat what people say as unattributed. You pass back themes, never names. The exception is conduct or the law, which goes to HR, and you say so up front.

### How do you start if your organisation has never had skip-levels?

Tell your managers first, then announce them to the whole group with the purpose and the rules. Make the first round informal. If it stays quiet, give it time: the questions may come in the second round, once people have seen that nothing bad happened after the first.

### How is a skip-level different from a town hall?

A town hall is you talking to everyone. A skip-level is a small group, or one person, talking to you. If you spend most of a skip-level talking, you've run a small town hall.

## Sources on getting a quiet room to talk

- *Impro* by Keith Johnstone. It's our source for skip-levels that go quiet. The room's gone quiet Playbook takes its ask for the three worst ideas from Johnstone. If you want the book itself, buy it from [Bookshop.org](https://uk.bookshop.org/a/17570/9781350069039?ref=playbooksforleaders.com) or [Amazon](https://www.amazon.co.uk/dp/1350069035?tag=thecustocouk-21&ref=playbooksforleaders.com).

*Some book links on this page are affiliate links. If you buy through one, we earn a small commission.*