Skip-level meeting questions that surface real issues

A skip-level — where you meet the people who report to your reports — is one of the most useful and most misused tools a senior manager has. Done well, it gives you an unfiltered read on how the org actually feels and works. Done badly, it makes your managers feel undermined and your engineers feel interrogated.

The difference is mostly in how you set it up and what you ask.

Set it up so it doesn’t backfire

Before the questions, get the framing right:

• Tell their manager first. Skip-levels done behind a manager’s back read as going around them. Loop them in — most good managers welcome it.
• State the purpose plainly. “I want to understand how things are going from your seat, and how I can make this a better place to work.” Not a performance check, not a backchannel.
• Protect confidence. Be clear about what you’ll do with what you hear. If someone shares something sensitive, you don’t carry it straight to their manager with their name on it.

Questions about their work

Start on solid, low-stakes ground — their actual experience of the job.

• What are you working on, and how do you feel about it?
• What’s the most frustrating part of getting your work done here?
• Is it clear to you how your work connects to what the company is trying to do?
• What would make you more effective that you don’t have today?

Questions about their manager

Ask these carefully and constructively. You’re not collecting evidence — you’re looking for where you can help your manager grow.

• What does your manager do that you find genuinely helpful?
• What do you wish they did more, or less, of?
• Do you get the context and feedback you need from them?
• When you’re stuck or struggling, do you feel you can go to them?

Questions about the team and the org

This is where skip-levels earn their keep — you hear things that never reach you through the normal chain.

• How’s the team’s morale from where you sit?
• Is there anything everyone knows but nobody’s saying out loud?
• What’s one thing you’d change about how we work if you could?
• Is there anyone you think deserves more recognition than they’re getting?

Questions about you and leadership

• What should leadership be paying more attention to?
• Is there anything I, or the people above your manager, are getting wrong?
• What would make you more confident about the direction we’re heading?

How to set up the invite

The framing in the meeting matters, but so does the framing before it — a cold “your skip-level wants to meet you” calendar hold reads as ominous. Send a short, warm note that says what it is and what it isn’t:

“I like to grab 30 minutes with everyone in the wider team now and then — nothing formal, and not a review. I’d just love to hear how things are going from your side, and what I could be doing better. Does a coffee chat next week work?”

Keep the first one low-stakes; you won’t get the real answers in meeting one anyway, because trust is built over a couple of conversations. Hold it somewhere relaxed if you can, let them steer, and resist the urge to take notes like an investigator.

How often to run them

Skip-levels work best as a light, regular rhythm rather than a one-off event. For a team of a reasonable size, meeting each person once or twice a year is plenty — often enough to build familiarity, rare enough that it never competes with their own manager’s 1:1s. Rotate through steadily instead of batching them into one anxious week. And if you only ever schedule a skip-level when something has already gone wrong, people learn to dread the invitation — the regularity is what keeps it safe.

What to feed back, and what to keep

You’ll often leave a skip-level holding something useful for the person’s manager — but how you pass it on determines whether anyone trusts you again. Never hand back a specific complaint with a name attached. Carry themes, not quotes: “a couple of people seem unclear on how priorities get set” is safe and actionable; “Priya said you don’t give enough context” is a betrayal that will travel. When something genuinely needs the manager’s attention and can’t be anonymised, ask first: “would you be okay with me raising this — and how would you like me to?”

The mistake that kills skip-levels

It’s worth saying plainly: the fastest way to ruin skip-levels is to use them to second-guess your managers. If an engineer raises a concern and your next move is to march over and relitigate it, you’ve done three bad things at once — exposed the source, undermined the manager, and taught everyone the skip-level is a trap. Your job with what you hear is to coach the manager and adjust the system, not to adjudicate grievances behind their back. Handled with that discipline, skip-levels are one of the best instruments a senior leader has; handled carelessly, one of the most destructive.

What to do with what you hear

The fastest way to poison skip-levels is to mishandle what comes out of them. Two rules: never betray a confidence in a way that’s traceable to the person, and always close the loop on themes. If three skip-levels surface the same problem, your engineers need to see something change — otherwise they learn that talking to you is pointless.

The themes are the real output. A single comment is an anecdote; the same comment from several people is a signal worth acting on. Holding those threads across many conversations — and making sure they turn into action — is exactly where a system helps. You can ask CoManager what’s come up across your team and get an answer grounded in your real notes and history, and the patterns that matter surface as ranked signals with a suggested next step — so the things people trusted you with actually go somewhere.