Skip-Level Meetings That Don't Feel Weird (Real Playbook)
- "What's something working really well that nobody outside the team would know about?"
- "If you had a magic wand, what's the one thing you'd change about how we work?"
- "What's a question you wish I'd ask?"
Skip-levels are awkward by default. Your direct report's report walks in nervous, wondering if they're being audited, evaluated, or told something about their boss. You walk in unsure how to fill 30 minutes without making it weird.
Done well, skip-levels are the highest-signal conversation you have all month. Done badly, they damage two relationships at once — yours with the report, and your direct report's with the person you just met with.
What a skip-level is for
A skip-level isn't a status update. It isn't a chance to grade your direct report's management. It isn't a HR conversation in disguise. If you treat it as any of those, the meeting is poisoned before it starts.
The actual purpose is twofold. One: gather signal you can't get from your direct reports. They filter what they tell you, even when they don't mean to. Their reports see things they don't. Two: give the more junior person visibility into how leadership thinks. They benefit from hearing your context. You benefit from hearing theirs.
Research on employee engagement consistently shows that visibility from senior leadership is among the strongest drivers of retention for high performers. Skip-levels are the cheapest version of that visibility you can run. A monthly 30 minutes returns more loyalty than most retention programs.
Take Bao, a VP of engineering who started doing quarterly skip-levels with every IC two layers below him. The conversations took eight hours total per quarter. Engagement scores in his org went from middle-of-pack to top-decile within two cycles. The conversations themselves were nothing fancy. The pattern of doing them at all changed how the team felt about being seen.
Why most skip-levels backfire
Three common failure modes lead to the "weirdness" that kills these meetings.
The first: making the meeting about evaluation. The senior leader walks in asking pointed questions that signal they're checking up on something. "Does Sarah give you enough feedback?" feels like an interrogation. The report leaves wondering what they said wrong or if Sarah is in trouble. Word gets back to the direct report manager. Trust erodes between layers.
The second: acting on what you hear immediately. Someone shares a frustration in a skip-level. You go fix it directly, bypassing your direct report. You've now signaled to the team that the way to get things done is to skip your manager. You've also told your direct report you don't trust them to handle their own team. Both messages travel fast and cause organizational debt.
The third: making it transactional. You ask for a list of what they're working on. They give you a status report they’ve already given their manager. You both look at your watches. The "skip" part of the level was wasted because you stayed at the surface level of the work rather than the depth of the culture.
The "No Surprises" Preparation
To remove the weirdness, you have to over-communicate the intent before the calendar invite even goes out.
The most important step happens with your direct reports (the managers). Tell them: "I'm starting skip-levels. My goal is to get closer to the ground-truth of the product and to make sure your team feels connected to our high-level strategy. This is not a performance review of you. If I hear something concerning, I will bring it to you directly so we can solve it together."
When you invite the IC, use a template that lowers the stakes: "Hi [Name], I’m doing skip-levels with the whole team to stay connected to what’s happening on the front lines and to share some of the bigger-picture context I’m seeing. This isn't a status update or a performance review—just a chance for us to chat. Here are the three questions I usually like to ask..."
By sending the questions in advance, you remove the "Am I in trouble?" anxiety.
The Script: Questions that actually yield signal
If you want signal, you have to ask questions that require a perspective, not just a fact. Here are four that work every time:
- "What is the one thing we do here that feels like 'unnecessary friction' to you?" This is better than asking "What's wrong?" It gives them permission to point at processes or tools that are slowing them down without blaming people.
- "What is something we should be talking about as a leadership team that you don't think is on our radar yet?" This treats them as an expert. It signals that you value their "ground-level" perspective.
- "If you were in my shoes for a week, what’s the first thing you’d change about how the department operates?" This is a classic for a reason. It forces them to think about the system, not just their tasks.
- "What’s the most confusing thing you’ve heard from leadership lately?" This is the ultimate test of your internal communication. If they tell you they don't understand the new quarterly goals, you know you have a cascading communication problem.
The Aftermath: Closing the loop
The biggest mistake is leaving the feedback in the room. If someone gives you a brilliant idea or points out a glaring problem, and they never hear about it again, the skip-level was a net negative. It feels like shouting into a void.
However, you must manage the "Middle Manager Triangle" carefully.
When the meeting ends, tell the IC: "Thank you for the honesty. I’m going to share these general themes with [Their Manager], but I won't attribute specific comments unless it’s something we need to solve together. My goal is to help [Their Manager] support you better."
Then, meet with your direct report. Do not say, "Jane said you don't give enough feedback." Instead, say, "I’m hearing a theme in my skip-levels that the team is looking for more frequent tactical feedback. How can I help you set up a rhythm for that?"
You are using the signal to coach your manager, not to convict them.
The Bao Case: A Practical Playbook
Let's look back at Bao, the VP of Engineering. His "8-hour quarter" worked because he followed a strict 30-minute template:
- 0-5 mins: Personal connection. (Not "How's the weather," but "What's the most interesting thing you've learned lately?")
- 5-15 mins: Context sharing. Bao would share one "behind the scenes" thing from the executive level—why a certain pivot happened or how a budget was decided. This builds incredible trust.
- 15-25 mins: The Signal. He would ask one of the four questions above. He would take physical notes to show he was listening.
- 25-30 mins: The "How can I help you?" Bao would ask if there were any resources or connections he could provide to help them in their career.
By the end of the year, Bao didn't just have better engagement scores; he had a map of the organization's real bottlenecks that his direct reports had been unintentionally smoothing over. He found out a specific legacy codebase was causing 40% of the team's stress—something that had never made it into a weekly status report.
Summary: From Weird to Essential
Skip-level meetings feel weird because they disrupt the hierarchy. But in a healthy organization, the hierarchy exists to support the work, not to gatekeep information.
When you approach these meetings with curiosity instead of judgment, and when you protect the "triangle" of trust between you, the manager, and the report, you turn a nervous 30-minute block into a strategic advantage. You see the cracks in the foundation before the building leans.
Is your team culture healthy enough for skip-levels, or would they feel like an audit right now?
Take our Organization Health Scan to see where your communication gaps are and get a custom playbook for building the trust required for high-signal leadership.