Done well, a skip-level gives you ground truth and gives your team a voice. Done badly, it feels like surveillance. The difference is almost entirely in how you run it.

You are three layers up from the work now. The reports you read are filtered, the all-hands is polished, and you have a nagging feeling you are the last to know when something is wrong.

That feeling is usually right. There is a line we use in our leadership programs that names it exactly: if there is more truth in the hallways of your organization than in your meetings, you have a problem. And by the time you are a few layers up, there almost always is.

Skip-level meetings are one way good leaders fix that, and one way clumsy ones accidentally torch their managers' trust. The definition is simple: you meet with someone two levels down, without their direct manager in the room. Done well, it gives you ground truth and gives them a voice. Done badly, it feels like an audit, and your managers start wondering why you are checking up on their teams.

The whole game is in how you run it. Here is how to run it well.

‍

The Problem: The Higher You Climb, the Less You Hear

Information decays as it travels up. Every layer smooths the edges. By the time a problem reaches you, it has been reframed two or three times by people who would rather not look bad, and you end up making decisions on a sanitized version of reality.

This has a name. Daniel Goleman calls it CEO disease: the information vacuum that forms around a leader when people withhold information, usually the unpleasant kind. It is not that anyone is lying to you. It is that bad news gets softened at every handoff by people who want to be seen as upbeat, or who fear the messenger gets shot. The result is the same. You get partial information about what is actually happening, and the more senior you are, the worse it gets. There is research showing that feedback becomes less reliable the higher a manager sits and the more complex their role.

So you miss things. You miss the brilliant idea sitting two desks away from the person who could green-light it. You miss the slow burnout of a team that looks fine on a dashboard. This is the quiet tax of scale.

The instinct is to ask your managers for more detail. But you cannot fact-check a filtered story by asking the person doing the filtering. You need a direct line to the source. That is what a skip-level gives you.

One reframe before the tactics, because it matters. Listening is not the thing you do in the meeting. It is a system you build. Adam Bryant and Kevin Sharer interviewed more than 600 leaders about how they actually stay informed, and the pattern was consistent: the best leaders build a listening ecosystem, a set of channels and rituals designed to surface the truth before it becomes a crisis. A skip-level is not the whole ecosystem. It is one reliable sensor inside it.

‍

The Insight: Skip-Levels Are for Listening, Not Inspecting

Here is the rule that decides everything. A skip-level is a listening tool, not an inspection. The moment it becomes a performance review of the manager who is not in the room, you have broken it.

When people feel heard by senior leaders, they show up differently. Salesforce research found that employees who feel heard are 4.6 times more likely to feel empowered to do their best work. That is the mechanism. Not "the boss came by," but "someone senior actually listened, and it changed how I show up."

But listening only works on a foundation of trust. If your team does not have psychological safety, a skip-level just produces nervous nodding. People tell you what they think keeps them safe. So the skip-level is not a substitute for safety. It is a test of whether you have built any. There is a deeper truth underneath this that Fahd puts simply: people are only unreasonable when they feel unheard. Give someone a genuine chance to be heard and they will stay reasonable even when you disagree with them. Deny it and you lose them, quietly, long before they tell you.

‍

The Trust Tightrope With Your Managers

Your managers will have one fear: that you are going around them. Name it before they do.

The fix is a rule you never break. You go to a skip-level to understand the system, not to evaluate the manager. You are listening for patterns, blockers, and ideas, not collecting grievances to act on behind someone's back. If something serious comes up, you coach the manager to address it. You do not swoop in and fix it yourself.

There is a reason that swooping is so damaging, and it goes deeper than hurt feelings. In our Empowerment Spectrum, every leader is somewhere on a path from Controlled to Managed to Coached to Empowered. When you reach over a manager's head and solve their team's problem, you yank that manager back toward Controlled in front of their own people. You have just told the team, in the clearest possible way, that real authority lives with you, and you have told the manager you do not trust them to hold it.

It also pulls decisions in exactly the wrong direction. The closer a decision sits to the work, the better it tends to be, because the person closest has the most context and the most skin in the game. Rescuing pulls decisions up and away from that person, toward you, who has the least direct context of anyone involved. This is the same accountability logic behind RACI and clear decision rights: the manager owns their team, and the skip-level just helps you see whether that ownership is working.

‍

What a Skip-Level Is Not

It is not a one-on-one. Your regular one-on-one rhythm is between a person and their direct manager, and it builds the day-to-day trust that drives the work. A skip-level is occasional, structural, and aimed at the system. Confuse the two and you will exhaust everyone.

It is also not a QBR. The quarterly business review is about decisions and numbers. The skip-level is about people and signal. Keep them separate, because the moment a skip-level starts tracking metrics, it stops surfacing truth.

‍

How to Run a Skip-Level That Works

Here is a playbook you can use this quarter. It takes about 30 minutes per person.

A few notes on the steps that matter most.

Telling the manager first removes most of the threat in one move. Frame it as listening, not auditing: "I want to hear how the team is doing and find blockers I can clear, and I will bring anything useful back to you." That single sentence turns a potential loyalty test into a gift.

Opening with safety, not status, is what separates a real skip-level from a stilted one. Do not start with "how is the project going." Start with "I am here to listen and help, not to grade anyone, and nothing you say gets your manager in trouble." Then mean it, because they will test whether you do.

The four questions should stay the same every time, so patterns show up across the year:

1. What is working that leadership might not see?
2. What is slowing the team down?
3. What would you change if you ran this team?
4. What do you hope never changes?

Closing the loop without betraying it is the final discipline. Within a few days, send a short note confirming what you heard. Then bring the themes, never the names, to the manager and coach them on the fixes. The team should see things get better without anyone ever feeling thrown under the bus.

Here is the kind of thing that surfaces when you run this well. A founder holds a skip-level with a team he assumes is fine. In 30 minutes he learns that a tooling decision is quietly costing the team a day a week. The manager had never raised it, because she thought it was settled. One skip-level, one fix, a day a week back, and the manager does not feel undermined. She feels unblocked. That is the whole thing working as designed.

‍

The Mistake That Ruins It

The fastest way to wreck a skip-level: hear a complaint, then go solve it yourself over the manager's head.

It feels heroic. It is corrosive. You just taught the team that the way to get things done is to wait for the big boss, and you taught the manager that you do not trust them. Do it enough and you become the bottleneck, which defeats the entire reason you climbed out of the weeds in the first place.

Bring it back. Coach, do not rescue.

‍

The Bottom Line

You will never out-run the information decay that comes with scale. CEO disease is structural, not personal, and it gets worse the higher you sit. But you can build a direct line to the truth without cutting the wire to your managers.

Tell the manager first. Listen more than you talk. Coach what you learn instead of fixing it yourself. Do that, and the skip-level stops being a threat to anyone and becomes the thing it should be: one quiet, reliable way to lead the whole system, not just the people in your inbox.

‍

Frequently Asked Questions:

‍