The Skip Level Meeting: What It Is For, and How to Run One

A calendar invite lands from your manager's manager. Thirty minutes, no agenda, the title is "Chat." That is a skip level meeting, whatever the invite calls it.

You do two things immediately. You check whether anyone else on the team got one. Then you try to remember what you said in the last all-hands.

The VP who sent it thinks they are being friendly. They will open with "this is informal, no agenda, I do these with everyone." Every clause is meant to lower the stakes, and together they raise them. Nobody announces "no agenda" about a meeting that genuinely has none.

A skip level meeting is either useful or quietly corrosive, with very little in between. What decides it is whether all three people know what the meeting is for, and whether the senior person has a rule about what happens to what they hear.

What a skip level meeting is, in plain terms

A skip level meeting is a conversation between an employee and their manager's manager, without the direct manager present. Thirty minutes is the normal length. A published rotation is the normal cadence.

It exists for three reasons, and it gets worse the moment you add a fourth.

The senior leader gets signal that has not been summarized. Information two levels up has passed through someone whose performance is partly what the information is about. That is compression, not dishonesty, and compression drops the parts that are hard to say.

The employee gets a real person attached to the priorities. Strategy in an all-hands is an announcement. Strategy from someone who will answer a follow-up question is a decision you can work with.

The organization stops running on one channel. If everything a VP knows about a team of thirty comes from one director, that director is a single point of failure.

How it differs from a one-on-one and from an escalation

• A one-on-one is with the person who writes your review and owns your problems. Weekly, and where things get fixed.
• A skip level is with someone two rungs up who does not manage your day. Occasional, and where patterns get noticed. Nothing gets fixed in the room.
• An escalation is an incident. Triggered by a specific problem, going around somebody on purpose, and everyone knows it.

The failure mode is letting the third one wear the costume of the second. If the only time you sit down with your skip is when something has gone wrong, you run escalations with a friendlier name, and your team has correctly learned that an invite from the VP means trouble.

If you are the senior leader running them

Cadence: boring, published, never in a burst

Once or twice a year per person is enough. With forty people two levels below you, that is two a month.

The order matters more than the frequency. Go alphabetically, or by team, or by start date, and publish the list. Predictability is the entire safety mechanism: someone who can see they were always going to be next in March does not spend the week before wondering what they did.

Never schedule a run of them right after a reorg, a bad quarter, or a resignation. Same meeting, same questions, completely different meaning.

Open so nobody thinks someone is getting fired

The first ninety seconds decide what you get for the next twenty-eight. Say why the meeting exists, where it sits in the rotation, and what you will do with what you hear, before you ask for anything.

A 30-minute skip level meeting agenda

Copy this. The times are the point: you will want to spend the first ten minutes explaining strategy, and that is exactly the meeting you should not run.

• 0:00 to 0:03. Frame it. The rotation, the purpose, the confidentiality rule, what this is not.
• 0:03 to 0:15. Their view of the work. Two or three questions and a lot of waiting. This is the block everything else exists to protect.
• 0:15 to 0:22. The system, not the people. Where things get stuck, what your level gets wrong, what they would change.
• 0:22 to 0:27. Their questions for you. Answer straight, including "I do not know" and "I cannot tell you that yet."
• 0:27 to 0:30. Agree what leaves the room. Item by item, out loud. Never skip this to reclaim three minutes.

Skip level meeting questions that get real answers

Pick four or five. Ask one, then say nothing for four seconds. The second thing somebody says is usually the true thing. The same waiting rule runs through good one-on-one questions.

About the work as it actually is:

• What are you working on right now that you think is a waste of time?
• What is the most annoying part of a normal Tuesday here?
• What do you know about this product that I clearly do not?
• What is the team working around instead of raising?

About decisions coming down from your level:

• Which decision from my level made the least sense by the time it reached you?
• What did we announce this year that changed nothing in your actual week?
• What do you think I am wrong about?
• What does everyone on the team know that nobody has told me?

About the parts of the org nobody maps:

• Where does work go to die here?
• Who helped you last month who will never get credit for it?
• If a recruiter called you tomorrow, what would make you pick up?
• What did you stop raising because nothing happened the last time?

Notice what is missing. There is no version of "how is Taylor doing as a manager?" That asks an employee to grade the person who writes their review, in front of the person who reviews that person. You get a polite answer, and you have taught them the meeting is a loyalty test.

What to do with what you hear

Wait for three. One person saying the release process is broken is a data point. Three people saying it in unrelated meetings is a fact about the company, and a fact can be acted on without a source.

Give most of it back to the manager, as a theme. Almost everything you hear is your director's job. Hand it over stripped of identifying detail: "I am hearing that decisions on the vendor stack sit for weeks. It came up more than once." If you cannot phrase it without the person being obvious, you are not ready to raise it.

Never act in a way that names the source without asking first. One rule, no exceptions, and it is worth the last three minutes of every skip level.

That is what makes the second round worth running. If nobody hears what came of the first, the second produces nothing but pleasant, careful noise.

If you are the manager whose reports are being skipped

The first time it happens it feels like an audit. Do the arithmetic before you react.

If your VP only ever hears about your team from you, your team's reputation rests entirely on your account of it. That sounds like control. It is exposure. The day a report says something to somebody senior at a happy hour, it lands like a revelation, because it is the first unfiltered thing they ever heard. Regular skip levels turn that from a bombshell into background.

Make them harmless by getting there first. Brief your team before the invite lands.

If you find out afterwards instead, do not debrief your report. There is no version of "so what did Dana ask about?" that does not read as checking whether you were mentioned.

If you want the themes, ask your skip, not your report. "I know you did four of these on my team, anything I should be working on?" is a fair question, and a leader who cannot answer it in general terms is running the meetings badly.

What should genuinely worry you is narrow: a change to your team that you learn about from your report rather than from your boss. That is not a skip level problem. It belongs in a direct conversation with your own manager.

If you are the employee being skipped

Go in useful. The people who get value out of these arrive with information, not grievances, and the whole difference is how specific you are.

Prepare two things. One that is working which they cannot see from two levels up, ideally with a name attached, because senior leaders get few chances to hear who is actually carrying something. One that is broken, with a concrete example and a date.

What not to bring: anything vague and negative. "Morale is low" cannot be acted on, and it tells the room more about you than about the problem. Leave out anything about a colleague you would not say with that colleague present. It will travel, and it will travel with your name on it.

The rule that solves the going-around-your-manager problem is simpler than people expect. Say it to your manager first. Then you get a sentence that costs you nothing.

That last move answers the question everyone actually has. Be honest about what you need, not about who your manager is. "I need decisions faster, here is the example" is something a VP can repeat without it being an attack. "Taylor is indecisive" is a judgment. It will reach Taylor eventually, and it will change nothing except how Taylor works with you.

One exception, and it is not subtle. Harassment, discrimination, or someone lying about numbers is not skip level material. That is HR, and a skip level is a bad substitute: no process, no record.

If the meeting turns into disagreement about a call already made, argue once, properly, then get behind it. That is what disagree and commit is for.

This does not work if the senior person cannot act on what they hear. A skip level where the VP has no budget, no say in the roadmap and no intention of revisiting a manager's decision is a complaints channel with no exit, and people work that out by the second round. If that is the situation, say so in the first three minutes: what you can change, and what you cannot.

Why reading this is not the same as saying it

All of this is easy to agree with on a page. It is different at 2:04 on a Tuesday, when someone two levels above you asks "so, how are things really going on the team?" and then stops talking.

The silence does the work. Most people fill it with the safe version, or with something sharper than they meant. Both come from the same place: no prepared sentence when the pressure arrives.

The fix is not more preparation on paper. It is having said the sentence out loud, at normal volume, with somebody pushing back, until "I have raised this with Taylor twice and we are stuck" comes out as a statement instead of an apology. Rehearsing in your head does not count. In your head, the VP nods.