By Andreas Pettersson, Founder, Leaders ADAPT
The most dangerous sentence a CEO hears is "I didn't want to bother you." By the time it reaches you, the thing you were not bothered with has usually been going on for months. Two layers down, somebody knew. Their manager knew a softer version. You got the version that survived the trip.
A skip-level meeting is the cheapest tool I know for shortening that trip. The rules on this page are the ones I published in The 5-Minute Leader and teach to the CEOs I advise, shaped by running a company that grew from a handful of people to more than 150, with teams in Europe, Japan and the US. This guide covers what a skip-level meeting is, what it is for, how often to hold one, what to ask, and the part most guides skip: what you do with what you hear without breaking the manager in the middle.
Quick answer: A skip-level meeting is a one-on-one conversation between a leader and an employee who reports to one of that leader's direct reports, held without the direct manager present. Its purpose is to hear how the work and the team feel from the person doing the work, unfiltered by the layer in between, and to check that the leader's priorities and standards survived the trip down the org chart.
What is a skip-level meeting?
A skip-level meeting is a scheduled one-on-one between a manager's manager and an employee two levels down, held without the direct manager, to hear the employee's experience directly. The name is literal: you skip one level of the org chart and talk to the person on the other side of it.
Three things make it a skip-level and not just a chat. It is scheduled, so nobody has to invent a reason to be in the room. It is one-on-one, so the answers belong to one person. And the manager in the middle is not there, which is the whole point and the whole risk.
People search for this under several names: skip-level meetings, skip-level 1:1s, skips, and in HR language a "skip-level" or "level-skipping" conversation.
What does a skip-level interview mean?
A skip-level interview is something else: a hiring step where a candidate meets the hiring manager's boss, usually late in the process, to check fit with the wider organization. Same org chart move, different purpose. This guide is about the meeting, not the interview.
What is the purpose of skip-level meetings?
The honest purpose is not "connection" or "visibility", the HR template words. It is to close a gap you cannot see from your seat.
I call it the Information Gap. The Information Gap is the distance between what is actually happening in your business and what makes it all the way up to you. It is not a flaw in your people. It is the natural, predictable side effect of being the person in charge.
Here is why it forms. Teams are pattern recognition machines. They learn fast that speaking up costs something and staying quiet costs nothing, and your A players learn it fastest.
Your reactions carry roughly ten times the weight you feel them at; you are operating at a volume you cannot hear. Every layer between you and the work edits the story a little. And when you show visible certainty, you teach the room that disagreement is friction. Psychological safety, in practice, is whether the person two levels down believes the last of those is untrue.
Four fingerprints tell you the gap already exists: surprises that other people saw coming, meetings that are too smooth, truth that reaches you sideways, and the phrase "I didn't want to bother you." If you have said "my door is always open" in the last month, that is often the clearest sign of all. Nobody walks through an open door to deliver bad news to the person whose reaction carries ten times the weight.
So the purpose of skip-level meetings, stated plainly, is to get past the filter on a schedule rather than by accident. You are checking whether your priorities survived the trip down, whether standards hold where you cannot see, and whether the people doing the work still have a way to tell you the truth.
Are skip-level meetings good or bad?
Both, depending on what you do with them. Employees ask this with a knot in their stomach; managers ask it with a different knot.
They are good when they are routine, announced, and clearly not about the manager. They are bad when they are rare, sudden, and used to audit someone who is not in the room. A skip-level that only happens when something is wrong teaches the whole company that a calendar invite from you is a warning shot.
The other failure is the smooth one: the team walks in calm, gives careful answers, and you leave with a script instead of the truth. A skip-level does not defeat the Information Gap by existing. It defeats it when the person across from you has evidence that telling you something unwelcome is safe. That evidence is built in the two seconds after they say it, which we will get to.
How often should you hold skip-level meetings, and how long?
The cadence rules I teach for one-on-ones apply here with one change: skip-levels are less frequent and never replace the manager's own meeting.
With direct reports, I want a coaching conversation at least every other week, and I have run them as short as fifteen minutes. A skip-level is quarterly for most people two levels down, as I wrote on the one-on-one meeting agenda page, and thirty minutes is enough if you do not fill it with your own talking.
Who gets one, from the rule I published in The 5-Minute Leader: high potentials, flight risks a manager may not see, new hires in critical roles after their first 30 days, and a random sample of everyone else. The random sample matters. If skip-levels only go to stars and problems, everyone can read the list.
Do the math on scale. A manager can typically run seven to ten direct reports. If you have five managers and forty people below them, a quarterly skip-level with a rotating sample of ten is about one 30-minute meeting a week.
If the number that came out felt heavy, cut the frequency, not the practice. Once a year for everyone beats quarterly for nobody, and the retention effect of being heard once a year by the person at the top is real.
How to run a skip-level meeting as the leader
Here is the structure I use. The full skip-level meeting template, with the agenda by minute, the invitation email and the note you send the manager afterwards, is on its own page.
Keep it from undermining the manager: tell them first
The manager hears about the skip-level from you, before the invite goes out, with the reason stated: standing practice, every team, themes shared afterwards. A manager who learns about a skip-level from their own report has already lost something you will not get back.
Open by naming what it is not
The first sentence out of your mouth sets the whole meeting. The one I published in The 5-Minute Leader: "This isn't about your manager. I want to understand your experience directly." Say it even when it is partly about the manager. It tells the person what kind of honesty is being asked for.
Ask four questions and then stop talking
What is working well. What is frustrating. What would you change if you could. Is there anything you are not comfortable telling your manager.
That last one gets asked at the end, after the first three have made the room safe. The full sequence, including what good and worrying answers sound like, is in the skip-level meeting questions page. In a skip-level you have not earned the meeting-to-meeting trust a direct manager builds, so start lighter than you would in your own one-on-ones. If you want your people to arrive ready, send them how to prepare for a skip-level meeting as an employee.
Master the two-second window
When the unwelcome thing arrives, the two seconds after it are the entire game. Your face, your first word, whether you defend or ask another question. Thank them before you evaluate, and ask one more question before you explain.
If you get this wrong once in front of a team, you re-chain the whole room and every skip-level after it produces the script, not the truth. Listening is not a soft skill here. It is the mechanism.
Write it down the same way every time
Date, energy from one to ten, key topics, what they need, red flags, what you committed to. If you are not documenting, you are not seeing patterns, and patterns are the only reason to do this at all.
What do you do with what you hear, including complaints about the manager?
Sort what you heard into three piles: the work (priorities, blockers, standards), the person (ambitions, energy, risk of leaving), and the manager.
The first pile goes back to the manager as themes, without names, the same week. "Two people mentioned the release process; worth a look." The manager fixes it and gets the credit. That is the feedback loop that makes managers stop fearing skip-levels.
The second pile is yours to hold and act on quietly: a stretch assignment, an introduction, a note to check again next quarter.
The third pile is the hard one. A complaint about the manager is data, not a verdict. Ask yourself whether the person raised it with the manager first; if not, that is usually your first coaching move, back toward the direct conversation. If it is a pattern, it is your job to manage the manager, hard, before you decide anything about them.
In the company I ran we separated the problem from the individual. The problem got talked about, the blame did not land on a person, and the people who raised the flag were celebrated for speaking up. The alternative is a blame culture where the problems go unheard and unseen.
The tripwire
One rule from The 5-Minute Leader that I would keep if I could keep only one: three skip-levels in a row saying "I don't really know what I own" or "my one-on-ones are just status updates" is not three people problems. It is a management problem, and it is yours to fix.
Skip-level meetings remotely and across cultures
I learned this running teams on three continents. The same four questions get very different answers in Tokyo, Stockholm and Los Angeles, and the differences are not about honesty.
Two dials matter: how direct a culture is, and how emotionally expressive. Japanese and much of Asian working culture sits on the indirect side. Swedes are more indirect and reserved than people assume. Danish, Dutch and German colleagues are very direct and not expressive.
Americans sit in the middle and expect to be met there. When I moved to the US and gave someone straight strengths-and-weaknesses feedback, I was told to sandwich the weakness, which was a shock to a Scandinavian.
This is a starting position, not a stereotype to apply. It tells you how far your default is from theirs before you open your mouth. With an indirect communicator, the fourth question gets asked as "what would you want your manager to know that is hard to say in a meeting" rather than "is there anything you can't tell your manager." Same question, a door instead of a spotlight.
Remote adds one rule: cameras on, because you cannot read energy through a black square. When I still cannot read someone, I ask for a color: green, yellow or red. People answer that honestly far more often than they answer "how are you doing."
Skip-level meeting versus one-on-one versus town hall versus survey
| One-on-one | Skip-level meeting | Town hall or all-hands | Engagement survey | |
|---|---|---|---|---|
| Who | Manager and direct report | Leader and an employee two levels down | Leader and everyone | Everyone, anonymously |
| Cadence | Weekly to biweekly | Quarterly to annually per person | Monthly or quarterly | Annually or twice a year |
| What it is good at | Coaching, commitments, growth | Hearing what the layer filters, checking standards | Broadcasting direction | Measuring the average |
| What it cannot do | See past the manager's own blind spots | Replace the manager's coaching | Hear anything back | Explain a number or hear an individual |
| Main risk | Becomes a status update | Undermines the manager if handled badly | Smooth questions, no truth | Results filed, nothing changes |
| Who owns follow-up | The manager | The leader, with themes to the manager | The leader | HR and the leader |
The skeleton of an effective one-on-one meeting survives into the skip-level: written context beforehand, one growth thread, one problem, visible commitments. What changes is the coaching block, which softens, and the purpose, which shifts from growing the person to hearing what the org chart hides. The prompts a manager uses in their own meeting, on one-on-one meeting questions, mostly work here too, with the depth earned more slowly.
Frequently asked questions about skip-level meetings
What is a skip-level meeting in simple terms?
A skip-level meeting is a one-on-one conversation between a leader and an employee who works for one of that leader's direct reports, held without the direct manager in the room. It is scheduled in advance, usually lasts about thirty minutes, and is used to hear how the work and the team feel from the person doing the work, without the filtering that happens as information moves up an organization.
What is the purpose of a skip-level meeting?
The purpose is to shorten the distance between what is happening in a business and what reaches its leaders. Skip-level meetings let a senior leader check that priorities and standards survived the trip down the org chart, hear concerns and ideas that a middle layer might soften or drop, spot flight risks and high potentials early, and give employees a direct line to leadership without going around their manager.
Are skip-level meetings good or bad for employees?
They are good when they are routine, announced in advance, and clearly not an audit of the direct manager. Employees get visibility with senior leadership and a safe way to raise issues. They become bad when they are rare or sudden, when the leader uses them to check on a specific manager, or when what is said in the room leaks back with names attached. Consistency and confidentiality decide which one an organization gets.
How often should skip-level meetings happen?
For most employees two levels down, quarterly to once a year is typical, with more frequent meetings for new hires in critical roles after their first thirty days, high potentials, and people a manager may not realize are at risk of leaving. Skip-level meetings are less frequent than a manager's own one-on-ones and never replace them. Thirty minutes is usually enough when the leader listens more than they speak.
What should you say in a skip-level meeting as the leader?
Open by stating what the meeting is not: it is not about the direct manager, and it is not a performance review. Then ask open prompts and listen. Four that work in sequence are what is working well, what is frustrating, what the employee would change if they could, and whether there is anything they are not comfortable telling their manager. Close by saying what you will do with what you heard.
What is a skip-level meeting in HR terms, and what else is it called?
In HR usage a skip-level meeting is a structured conversation between an employee and their manager's manager, sometimes called a skip-level one-on-one, a skip-level 1:1, or simply a skip. It is distinct from a skip-level interview, which is a hiring step in which a candidate meets the hiring manager's boss. HR teams often document skip-level programs with a cadence, a standard agenda, and a rule on how feedback is shared with managers.
The rule that makes the whole practice worth it
Skip-level meetings do not fix the Information Gap because you scheduled them. They fix it when the person two levels down leaves the room with evidence that telling you something unwelcome was safe, and when their manager gets the themes back the same week and fixes something with them. Do those two things for a year and the sentence "I didn't want to bother you" disappears from your company. Skip either one and you will have bought yourself a very polite quarterly performance.
One action for this quarter: pick ten people you have never spoken to alone, tell their managers why, and run the four prompts. Then read your notes side by side and look for the third repeat.
If you lead managers, or you lead the whole company
The 5-Minute Leader is the system I wrote for leaders who are short on time: the one-on-one protocol the skip-level borrows from, the delegation checks that tell you whether authority actually moved down the chart, and a scaling section for leaders who manage managers. It is where the four prompts above come from. Start with The 5-Minute Leader.
If you are the CEO and the gap you are staring at is between you and your leadership team, that is a different conversation, and the one I have most often in 1:1 CEO advisory. The first session is a diagnostic of where information is stopping in your company, and it usually begins with what your last skip-level meeting did or did not tell you, before either of us decides whether to work together.
Andreas Pettersson was one of Canon's youngest CEOs, running an AI company that grew to more than 150 people with teams in Europe, Japan and the US. He was a tech CEO for 10 years and now advises CEOs and their leadership teams at Leaders ADAPT.
