The Meeting That Changed Everything

When Lena’s director announced she’d be scheduling skip-level meetings with each of Lena’s direct reports over the next month, Lena’s first reaction wasn’t curiosity. It was panic.

She’d been managing her team of eight for two years. Results were solid. Retention was decent. Nobody had escalated anything. But the idea of her boss sitting in a room with her people, asking what was and wasn’t working — without her there — triggered every insecurity she thought she’d outgrown. Was someone unhappy? Was this a quiet performance investigation? Was she about to find out what people were saying about her when she wasn’t in the room?

What followed was a week of over-compensation. Lena started checking in with her team more often — which her team noticed and found strange. She rehearsed what she’d say if her boss asked about specific team members. By the time the first skip-level happened, she’d created exactly the kind of tension these meetings are supposed to reduce. The meetings she feared weren’t the problem. Her reaction to them was.

This scenario plays out constantly. Gallup data shows that 70% of the variance in team engagement traces back to the direct manager — but the direct manager can’t always see what’s happening from their own vantage point. Skip-level meetings exist to fill that gap. The problem is that most organizations introduce them poorly, leaving middle managers feeling surveilled and employees unsure what they’re supposed to say.

Why Skip-Level Meetings Matter More Than Most Managers Think

U.S. employee engagement fell to just 31% in 2024, the lowest level in a decade. The primary drivers of disengagement — lack of recognition, unclear expectations, poor manager relationships, and absence of career development — are exactly the issues that surface in skip-level conversations but often stay buried in standard reporting.

The math is straightforward. Your direct reports tell you what they think you need to hear. Their direct reports tell them a filtered version of reality. By the time information reaches you, it’s been through two rounds of translation. Skip-level meetings cut through that.

Google’s Project Aristotle research found that teams with high psychological safety had a 76% higher rate of innovation. But psychological safety isn’t just about what happens within a team — it’s about whether people feel safe being honest with leaders at every level. When a senior leader makes time to listen directly, it signals that the organization values candor over hierarchy.

There’s a retention angle too. Organizations with high employee engagement experience 21% to 51% less turnover depending on their industry baseline. Skip-level meetings, done right, are one of the most efficient ways to spot disengagement before it becomes a resignation letter.

But here’s the part most articles won’t tell you: skip-level meetings are dangerous when handled wrong. If the senior leader uses them to second-guess the middle manager’s decisions, or if employees learn they can go around their boss to get what they want, you’ve just blown a hole in your management structure. The meetings become a weapon instead of a tool.

The Two-Hat Framework for Skip-Level Meetings

After 25 years of running these — and being the manager who got “skipped” — I’ve developed what I call the Two-Hat Framework. It addresses the reality that most managers will play both roles at different points: the senior leader running skip-levels, and the middle manager whose team is being met with.

Hat One: Running the Skip-Level (You’re the Senior Leader)

Set the table with your manager first. Before you schedule a single meeting, sit down with the manager you’re skipping over. Explain the purpose, the questions you plan to ask, and what you’ll do with the information. This isn’t optional — it’s the single most important step. Tell them: “I’m doing this to get a broader view of how the team is doing. I’m not evaluating you. I’ll share themes with you afterward, never individual attributions.”

Follow the 70/30 rule. You speak 30% of the time, maximum. This is a listening session. The best skip-level questions are open-ended:

• What’s working well on the team right now?
• What’s one thing that slows your work down that you wish someone would fix?
• Do you feel like you’re growing in your role?
• What would you want me to know that I probably don’t?

Aggregate, don’t attribute. After your meetings, group feedback into themes. Never say “Sarah told me you don’t give enough feedback.” Instead: “A theme I heard was that people want more regular feedback. How does that land with you?” This protects trust on all sides.

Close the loop. Salesforce research shows employees who feel heard are 4.6x more likely to feel empowered. But “heard” means action followed the conversation. Send a brief summary to participants: “Here’s what I heard, here’s what we’re doing about it.” Feedback without follow-through is worse than no feedback at all.

Hat Two: Being Skipped Over (Your Boss Meets Your Team)

Don’t coach your team beforehand. The temptation to prep your people — “Make sure you mention the new process we launched” — is enormous. Resist it. Your boss will see through coached responses instantly, and your team will resent being managed into a performance.

Ask for the debrief. If your boss doesn’t proactively share themes, request the conversation. Frame it as partnership: “I’d love to hear what themes came up so I can act on them.”

Don’t punish honesty. If you learn that someone raised a concern about your leadership in a skip-level, your only job is to get curious, not defensive. The moment someone faces consequences for being honest in a skip-level meeting, the entire system breaks down — and your credibility breaks with it.

Use it as data. Think of skip-level feedback the same way you’d think about a 360-degree review — it’s a signal, not a verdict. Look for patterns. If three people mention unclear priorities, that’s worth investigating. If one person has a complaint that contradicts everyone else, that’s context, not crisis.

Real-World Application: When Skip-Levels Go Right and Wrong

The Wrong Way: Priya, a director of operations, decided to run skip-levels after hearing about them at a conference. She scheduled meetings with her managers’ direct reports but didn’t tell her managers first. In the meetings, she asked pointed questions about her managers’ effectiveness. One employee mentioned that their manager, Kevin, was slow to approve time-off requests. Priya called Kevin immediately after and told him to fix it, naming the employee.

The result: Kevin felt ambushed and humiliated. The employee who spoke up got the cold shoulder for weeks. Other team members heard what happened and decided that skip-level meetings were a trap. Priya’s managers started operating defensively, hoarding information and managing up instead of leading their teams.

The Right Way: Six months later, Priya tried again — this time following the Two-Hat Framework. She met with each of her three managers first, explained the purpose, and agreed on the ground rules. She held 30-minute one-on-ones with eight employees over two weeks. She listened more than she talked. She took notes on themes, not individuals.

In her debrief with each manager, she shared aggregate patterns: “The team feels strong about project clarity but wants more frequent recognition for good work. Several people mentioned wanting more career development conversations.” No names. No gotchas.

Kevin, the same manager from the first attempt, actually appreciated it this time. “It helped me see what my team cares about without me having to drag it out of them in 1-on-1s,” he told Priya. The team saw changes happen within two weeks and started viewing skip-levels as an asset, not a threat.

How to Start Today

If you’re a senior leader: pick one team and schedule your first skip-level meeting this week. Before you do, spend 15 minutes with that team’s manager explaining the purpose and the ground rules. Use three of the four questions from the 70/30 section above. After the meeting, write down two to three themes — not individual quotes — and share them with the manager within 48 hours.

If you’re the manager being skipped: reach out to your boss proactively and say, “I think skip-level meetings would be valuable for our team. Want me to help set them up?” That single act transforms you from a passive participant to a partner in the process — and it shows leadership initiative that senior leaders notice.

Either way, start small. Two to three skip-level meetings per quarter is enough to build the muscle without overwhelming anyone’s calendar.

FAQ

How often should skip-level meetings happen?

For most organizations, once or twice per quarter is the right cadence. Running them too frequently can create the impression of surveillance and exhaust everyone’s calendars. The exception is during periods of significant change — a reorg, a new strategy rollout, or after a round of layoffs — when more frequent check-ins help leaders stay connected to ground-level reality.

What if an employee reports a serious issue about their manager in a skip-level?

Handle it carefully. If the concern involves harassment, discrimination, or policy violations, you have a legal and ethical obligation to escalate to HR immediately — regardless of your promise to aggregate feedback. For performance issues, coach the manager privately using the theme-based approach rather than attributing the feedback to a specific employee. Protecting the reporter’s identity while still addressing the problem is the line you need to walk.

Should middle managers be worried about skip-level meetings?

Not if they’re done right. A well-run skip-level actually helps middle managers by surfacing issues their team might not raise directly with them. The managers who should be concerned are the ones actively hiding problems from their leadership — and those problems need to surface anyway. If your boss announces skip-levels and you feel anxious, ask for the ground rules upfront. That conversation alone will tell you whether this is a partnership or an investigation.

Can skip-level meetings replace regular 1-on-1s?

Absolutely not. Skip-level meetings happen a few times per year and serve a different purpose — organizational health and cross-level connection. Regular 1-on-1 meetings between a manager and their direct reports should happen weekly or biweekly and remain the foundation of your people management rhythm. Skip-levels supplement that relationship; they don’t substitute for it.

How do I handle it when skip-level feedback contradicts what my manager tells me?

Treat it as a signal to dig deeper, not as proof that someone is lying. Different vantage points produce different perspectives — that’s the whole point. The most productive response is to share the discrepancy with your manager in a non-accusatory way: “I heard X from the team, and you’ve been telling me Y. Help me understand the gap.” Often the truth sits somewhere in the middle, and the conversation itself is where the value lives.