Skip-Level Meetings: When They Help and When They Backfire
Skip-level meetings help when the goal is information and they backfire when the goal is control. A leader who meets with employees two levels down to understand what the work is actually like will learn things no status report contains. A leader who uses the same meeting to check up on a manager, gather evidence, or quietly redirect work has created a parallel reporting line that undermines the manager and teaches the team who to go around. The mechanics look identical from the outside. This guide covers the difference, how to run one that works, and the specific ways they go wrong.
Note: This article is general management guidance, not legal advice. If a skip-level surfaces a complaint about harassment, discrimination, retaliation, wages, or safety, that triggers separate obligations and should be routed into a formal process rather than handled in the conversation.
Last reviewed: September 2026.
What a Skip-Level Actually Is
A skip-level is a conversation between a leader and someone who reports to one of their managers, held without that manager present. In a small business it is often the owner talking to a crew member, a technician, or a front-desk employee directly.
The purpose is a specific kind of information that does not survive the trip up the hierarchy: what slows the work down, which processes people quietly work around, whether the priorities you announced are the priorities being acted on, and what the team's experience of being managed actually is. Every layer filters, not out of dishonesty but because managers summarize, and summaries drop exactly the friction you need to hear about.
What it is not: a status update, a performance review, a way to assign work, or a channel for complaints about a manager that bypasses any real process. Each of those uses turns a useful practice into a destructive one.
Free Skip-Level Cadence Planner
What Cadence Can You Actually Sustain?
Work out how long a full rotation takes and what it costs you per month.
When They Help
You are too far from the work. Once a business passes the point where the owner sees everything, information arrives pre-digested. Skip-levels restore a direct channel without requiring you to hover.
You are about to change something. Before a process change, a new system, or a reorganization, the people doing the work know which parts will break. Asking them first costs an hour and saves months.
You are developing managers. Consistent patterns across a manager's team tell you where that manager needs support, and coaching based on what you heard is far more useful than coaching based on what they self-report.
Retention is slipping. People rarely announce that they are leaving until it is decided. They do mention, months earlier, that they have not learned anything in a year or that a process is grinding them down.
The company has grown quickly. New layers form fast in a growing business, and skip-levels are one of the few ways to notice when a layer has stopped transmitting.
When They Backfire
When the manager finds out afterward. The single fastest way to damage a manager is to meet their team without telling them. Even a benign conversation reads as an investigation once it was concealed.
When you start assigning work. A suggestion from two levels up is heard as an instruction. The employee now has two sets of priorities and will follow yours, which quietly strips the manager of authority.
When they only happen around trouble. If skip-levels appear when there is a problem, the meeting itself becomes a signal. People clam up and managers panic.
When you become the appeals court. If employees learn they can route around their manager by talking to you, they will, and the manager stops being able to manage. Hearing a complaint is fine; resolving it directly is not.
When nothing ever changes. Asking people what is broken and then doing nothing is worse than not asking. The second round of meetings gets superficial answers, because the first round taught everyone the exercise is cosmetic.
When you repeat what you heard. Quoting an employee to their manager, even approvingly, ends candor permanently. Everyone finds out.
How to Run One That Works
Tell the manager first. Explain that you are running skip-levels across the team, what you are asking about, and what you will do with it. Ideally they help schedule them. A manager who is told is an ally; a manager who finds out is an enemy.
Make it routine rather than reactive. A rotation everyone knows about removes the signal value. Nobody panics about a meeting that happens to everyone twice a year.
Keep it short and consistent. Thirty minutes, the same handful of questions for everyone, so patterns are visible across conversations.
Ask about the work, not about the person. "What slows you down" produces better information than "how is your manager," and the manager questions get answered anyway, indirectly and more honestly.
Listen more than you talk. The failure mode for owners is using the meeting to explain strategy. If you are talking more than a third of the time, it is not a skip-level.
Close the loop publicly. Report back to the whole group on themes and what you are changing, without attributing anything. This is what makes the next round produce real answers.
Questions Worth Asking
- What takes longer than it should?
- What do you work around because the official way does not work?
- What would you change if it were your call?
- What do you think our top priority is right now?
- Where do you get stuck waiting on someone else?
- What have you learned in the last six months?
- What is something people here complain about that leadership does not know?
- Is there anything you have raised before that never went anywhere?
What to Do With What You Hear
Sort it as you go. Some items are individual and belong back with the manager as coaching, carefully and without quoting. Some are systemic, appearing across multiple conversations, and those are yours to fix. And some are complaints about a specific manager's conduct, which is different from feedback about their style.
That last category needs care. If what surfaces is potential harassment, discrimination, retaliation, a wage issue, or a safety concern, the skip-level is not the venue and you cannot unhear it. Move it into your formal complaint process, tell the employee that is what you are doing and why, and follow the process from there.
For everything else, the rule is to act on themes rather than on individual reports. Three people describing the same bottleneck is a finding. One person's frustration is a data point, and acting on it immediately is how employees learn that the fastest way to get something changed is to complain to the owner.
If You Are the Manager Being Skipped
The instinct is to read it as a threat. Usually it is not, and reacting as though it is guarantees the outcome you fear.
Ask what the purpose is and what will come back to you. Offer to help schedule them, which signals confidence. Do not ask your team what was discussed afterward, because that single question destroys the value of the exercise and tells your team you are monitoring them. If your leader starts assigning work in those meetings, raise it directly and early, since that is a real problem and it will not fix itself.
If skip-levels only started after something went wrong, ask about that too. Better to know whether you are being evaluated than to guess for three months.
Common Mistakes
- Running them secretly. The concealment does more damage than anything said in the meeting.
- Only meeting with people who are struggling or complaining. Skews the picture and marks the participants.
- Turning it into a status update. You already have those, and they crowd out the only information the meeting was for.
- Making promises in the room. "I'll fix that" from two levels up creates an expectation you may not control.
- Doing them once. A single round is an audit. A rotation is a practice.
- Taking action on one person's version of a conflict. You have heard one side, and the manager has not been asked.
- Treating a legal complaint as feedback. Once it is raised, the obligation attaches whether or not the meeting was the intended venue.
Where a System Helps
Skip-levels tell you things a system cannot: how the work feels, what people work around, whether the priorities landed. But they work better when you arrive already knowing the facts, so the conversation can be about the parts that are not in any record.
In Updoot, projects and tasks roll up by owner and status, so you can see what someone is carrying before you sit down rather than spending the meeting establishing it. eNPS surveys give you the trend line between rotations, which is what tells you whether the themes you heard are improving or whether you asked good questions and then changed nothing.
Frequently Asked Questions
A conversation between a leader and an employee who reports to one of their managers, held without that manager present. The purpose is to hear about the work directly, since information gets summarized and smoothed as it moves up through layers. It is not a status update, a performance review, or a way to assign work, and using it for any of those turns a useful practice into a harmful one.
Always. Meeting someone's team without telling them is the fastest way to damage a manager, because even a benign conversation reads as an investigation once it was concealed. Explain that you are running a rotation, what you will ask about, and what you will do with what you hear. Having the manager help schedule them signals that this is routine rather than an inquiry.
Twice a year per person is a realistic target for most small companies, with 30-minute conversations on a published rotation. The test is whether your rotation math works: if the number of people and the meetings you can hold each week means everyone gets one every two years, the cadence is not real. Shorten the meetings, narrow the group, or use small group sessions instead.
Ask about the work rather than the person: what takes longer than it should, what people work around because the official process does not function, what they would change, what they believe the current priority is, and whether anything they raised before went nowhere. Use the same questions for everyone so patterns are visible across conversations. Manager questions get answered indirectly and more honestly this way.
Most often because they are run secretly, used to assign work, held only when something has gone wrong, or followed by no visible change. Each of those converts an information-gathering conversation into a parallel reporting line that undermines the manager and teaches employees to route around them. Repeating what an employee said to their manager ends candor permanently, and word always gets around.
Move it into your formal process immediately. Potential harassment, discrimination, retaliation, wage, or safety issues carry obligations that attach once the employer is on notice, regardless of the setting in which they were raised. Tell the employee what you are doing and why, avoid promising confidentiality you cannot deliver, and do not attempt to resolve it inside the conversation.
Final Takeaway
Tell the manager, run them on a rotation everyone knows about, ask about the work rather than about people, listen more than you talk, act on themes rather than individual reports, and report back on what you changed. Skip-levels fail for one of two reasons: they were secret, or they produced nothing. Both are avoidable, and the practice is one of the few ways a growing business keeps hearing what a leader can no longer see directly.