Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Run a Skip-Level Meeting That Actually Works
Transcript
- Lucas: Let me start with a number that still bothers me. A VP of Engineering I know lost three senior engineers in six months. All three gave exit interviews that said basically the same thing: they loved their work, liked their direct manager, but felt invisible to the person two levels up. Luna: Ouch. And that VP probably thought he was doing fine because his direct reports weren't complaining. Lucas: Exactly. And that's the trap. When you manage managers, your feedback loop gets filtered. The skip-level meeting is the only way to get unfiltered signal—and most managers skip it because it feels awkward. Luna: Yeah, or they worry it'll undermine their direct reports. Like they're going behind someone's back. Lucas: That's the biggest fear I hear. But if you approach it right, it actually strengthens the chain. Today I want to walk through a specific framework that turns the skip-level from a weird obligation into the most valuable hour on your calendar. Lucas: And before we dive deeper—if this conversation is landing for you, if it's helping you think through a management challenge you're facing right now, honestly, that's the whole point. The show stays ad-free because listeners who find it valuable occasionally chip in at buy me a coffee dot com slash fexingo. No pressure, ever. Just a light way to keep the coffee brewing. Luna: And it genuinely makes a difference. We hear from listeners who say an episode helped them handle a tough conversation or keep someone from quitting. That's the fuel. Lucas: Anyway—back to skip-levels. The first rule is: never have a skip-level without your direct report knowing it's happening and why. Luna: Right. Transparency protects trust. So you tell your manager: 'I'm going to have a quick chat with your team member to understand how things are going from their perspective. I'll share any general themes I hear, but I won't repeat specifics.' Lucas: Exactly. And then you ask the skip-level three questions. Question one: 'What's one thing about this team that you'd want the person two levels up to know?' That's wide open. It lets them surface whatever is top of mind—could be a process bottleneck, a win, a frustration. Luna: Question two: 'What's something your manager does that you wish more managers would do?' That's positive framing. It makes the feedback actionable without putting the person on the spot to complain. Lucas: And question three: 'What's one thing you'd change about how our team operates if you could?' That one surfaces systemic issues—stuff that's invisible from two levels up because it's so ingrained in the team's daily rhythm. Luna: I love that the third question is about the team, not the individual. It depersonalizes it. Lucas: Exactly. And here's the critical follow-up: after the meeting, you send a brief email to both the skip-level and their direct manager, summarizing the general themes—without attribution. You say something like, 'I heard that people feel the sprint cycle is too compressed, and there's appreciation for how the team celebrates wins.' That's it. No names. Luna: And what do you do if the skip-level raises a serious issue about their manager? Like, their manager is micromanaging or playing favorites? Lucas: You don't react in the moment. You listen, thank them, and say you'll take it seriously. Then you go to the manager—your direct report—and say, 'I'm hearing some concern about how decisions are being made on your team. I want to help you figure out what's happening.' You coach, you don't accuse. Luna: That's the hard part. It's tempting to jump in and fix it yourself, but that undermines the manager. Lucas: Right. Your job is to strengthen the manager, not replace them. And the skip-level meeting, done right, actually makes your direct reports better managers because they get real feedback they might not hear directly. Luna: So how often should you do these? Quarterly? Monthly? Lucas: I'd say quarterly for stable teams, monthly for new teams or teams under stress. But consistency matters more than frequency. If you do it once and never again, it feels like a check the box exercise. Luna: And the length? I've seen people try to do 15 minutes and it feels rushed. Lucas: Thirty minutes is the sweet spot. Fifteen is enough for the three questions if you stay on track, but thirty lets you go deeper if they open up. And always leave the last five minutes for them to ask you anything. Luna: That's a good capstone. 'Is there anything you want to ask me?' That flips the power dynamic. Lucas: Absolutely. And the number one thing to avoid: don't use the skip-level to give feedback about the manager. That's a trap. The moment you say, 'I think your manager should communicate more clearly,' you've just undermined the entire relationship. Luna: Right. You take that to the manager directly, not to their report. Lucas: So let's tie it back to that VP of Engineering. What he started doing was a quarterly fifteen-minute call with each engineer two levels down. Just the three questions, no agenda. Within a year, his attrition dropped to almost zero. And he told me that the biggest surprise was how many good ideas came from those conversations—ideas his direct reports had never passed up because they didn't think they were important enough. Luna: That's the hidden value. Skip-levels aren't just a retention tool—they're an innovation channel. Lucas: Exactly. And the cost is so low. Thirty minutes a quarter. If you manage ten managers, that's five hours a quarter for a direct line to fifty people. That's a pretty good return. Luna: So the takeaway: be transparent, use the three questions, summarize themes, and don't interfere. That's the recipe. Lucas: That's it. And if you're already doing skip-levels, I'd love to know what questions you ask. We might dedicate a future episode to the best skip-level questions from listeners. Luna: Alright. Next week we're tackling something I know a lot of managers struggle with—how to handle a team member who's coasting. Not performing poorly, just doing the minimum. Lucas: The quiet quitter who never quite quit. That should be a good one. Until then, keep the conversations real.