A VP asks her manager how the team is doing. “Good, all good,” he says. Three weeks later, two people quit in the same month and cite “management” as the reason on their exit forms. Nobody saw it coming, because nobody actually asked.
This is the gap skip-level meetings are built to close. A skip-level meeting is a conversation between a leader and someone two or more rungs below them on the org chart, without that person’s direct manager in the room. It sounds simple. Most organizations still don’t do it, or do it so rarely that it stops working as a signal and starts feeling like a special event.
What a skip-level meeting actually is
A skip-level meeting is a structured conversation between a manager’s manager and an employee who doesn’t report to them directly. The direct manager isn’t present. The point isn’t to bypass that manager permanently – it’s to hear, at least occasionally, what an unfiltered version of “how’s it going” sounds like.
That distinction matters. A skip-level isn’t a performance review, and it isn’t an invitation to complain about a specific coworker. Done well, it’s closer to a pulse check on team health, conducted by someone senior enough to actually act on what they hear.
Why annual surveys don’t catch this stuff
Most companies already run an engagement survey once or twice a year. So why bother with another feedback channel?
Because surveys are aggregated, anonymous, and delayed. By the time a culture problem shows up as a dip in a survey score, it’s usually been simmering for months. A skip-level conversation, by contrast, happens in real time, with a real person, about a real situation. You lose the statistical tidiness of a survey. You gain specificity – names, dates, patterns you can actually trace.
There’s also a filtering problem that surveys share with regular reporting lines. Employees are reluctant to criticize the person who signs off on their raises and promotions, and managers – especially newer ones – will often shape what reaches leadership, sometimes without meaning to. It’s not usually malice. It’s self-preservation, and it’s completely human. SHRM’s guidance on senior managers running skip-levels points to exactly this: teams under a struggling manager will often say very little through normal channels, right up until turnover spikes and the pattern becomes impossible to ignore.
What skip-levels catch that other channels miss
I’ve watched leadership teams treat culture problems as sudden events – a wave of resignations, a viral internal complaint, an anonymous letter to HR. They’re rarely sudden. They’re slow leaks that finally reached a visible level.
Skip-levels are one of the few structures built to catch the leak early. A few things tend to surface in these conversations that don’t show up anywhere else:
Cross-team friction that a direct manager either doesn’t see or doesn’t want to escalate. A rising performer who’s invisible to their own manager but obvious to anyone who talks to the wider team. Early signs of burnout that get masked in status updates because “everything’s manageable” is the safe thing to say in a 1:1 with your boss. And plain cultural drift – the slow shift in how a team talks about the company, their work, or each other, long before it hits an engagement number.
Ron Ashkenas has written about how leaders become “out of touch” as layers of management filter what reaches them, and recommends skip-level meetings specifically as a corrective – a point echoed in a Forbes Coaches Council piece on using skip-levels to stay connected to team culture. The meetings aren’t a replacement for good management. They’re a check on the fact that even good managers can’t see everything, and information degrades a little at every layer it passes through.
How to run one that surfaces real issues, not venting sessions
The mechanics matter more than most leaders expect. Get them wrong and a skip-level becomes either an ambush (bad for the manager) or a gripe session (bad for everyone, and rarely actionable).
Tell the manager it’s happening: Not the specifics of what gets discussed – just the fact that the meeting exists. Skip-levels that happen in secret erode trust fast, and once a manager finds out they were talked about behind their back, they stop trusting the process, even if nothing negative was said.
Frame the purpose before you ask a single question: Say plainly that this isn’t about building a case against their manager. It’s about understanding the team’s day-to-day reality and the employee’s own effectiveness – their manager is part of that picture, not the whole point of the conversation.
Keep the agenda short: Three to five questions from you, with most of the time left for whatever the employee brings up. This isn’t a status meeting.
Protect confidentiality, and mean it: If specifics leak back to the manager, word travels fast, and the next skip-level in that department will get nothing but safe, rehearsed answers.
Follow up on something: Even one visible action – adjusting a process, addressing a workload issue, checking back in a month – signals that the conversation had a point. Skip-levels with no follow-through train people to stop bothering.
If your organization already runs regular one-on-ones between managers and their direct reports, skip-levels aren’t a replacement for that rhythm – they’re a different altitude. One-on-ones tell a manager how their own reports are doing. Skip-levels tell senior leaders how the manager layer itself is doing, which is a much harder thing to self-report.
Common mistakes that undo the whole exercise
The biggest one is scheduling skip-levels once, treating them as a checkbox, then not doing them again for a year. Trust in this format builds slowly and evaporates fast. If people say something honest and then watch nothing change, they’ll treat the next invitation as theater.
The second is letting the meeting turn into an unofficial performance review of the manager, conducted through the back door. Employees pick up on this instantly, and it makes them far more cautious about what they’ll say – which defeats the entire purpose.
The third is canceling. Repeatedly bumping a skip-level sends a specific message: this wasn’t actually a priority. If leadership treats these meetings as disposable, they’ll get disposable answers in return, right up until the culture debt – the slow accumulation of small issues an organization has ignored, tolerated, or quietly excused – comes due all at once.
Questions worth asking
Start broad, then get specific. A few that tend to open honest conversation without putting anyone on the spot:
How would you describe the health of this team day to day? What’s something you wish leadership understood about how work actually happens here? Where do you see friction between teams that might not be visible from where I sit? Is there anything getting in your way that your manager may not be able to fix alone? What’s one thing that would make your work noticeably easier?
Notice what’s missing: nothing that asks someone to name and rate their manager directly. That’s not the point, and asking it that way almost guarantees a guarded, unhelpful answer.
What to do with what you hear
A skip-level is only as useful as what happens after it ends. Patterns matter more than single data points – one comment about workload is an anecdote, five similar comments across a team in one quarter is a signal worth acting on.
That’s the real value of the format. It’s not a substitute for structured culture assessment, but it’s one of the few tools that gets you unfiltered, real-time context between the bigger checkpoints. Pair it with a proper engagement survey and an honest look at where culture debt has quietly built up, and you get something close to an accurate picture of what it’s actually like to work at your company – not the version that survives three layers of management on its way up.
