Skip-Level Meetings: When and How
Your skip-level invite lands on a Tuesday. You’re an IC: your boss’s boss wants 30 minutes “to hear how things are going.” You rewrite your talking points three times. Say too little and you waste the slot. Say too much about your manager and you wonder if you just started a problem you can’t control.
Or you’re the director: you want signal from the floor, not a filtered status deck. Your managers are nervous. People in the room are careful. You leave with polished answers and almost no new information.
A skip level meeting can fix that gap, or it can train people to perform and triangulate. The difference is the contract you set before anyone talks.
What a skip-level meeting is (and why leaders hold them)
A skip-level meeting is a conversation between a leader and someone one or more levels below their direct reports. It may be a skip level 1:1, a small group, or a rotating series across the org.
Leaders use them to spot patterns status meetings miss, test whether strategy is landing, offer visibility without waiting for a crisis, and learn what middle managers need from above.
They are not a secret performance review of the middle manager, and they are not open office hours. Office hours are optional drop-ins. Skip-levels are intentional samples with a purpose, a cadence, and a loop back to managers.
Announce the rules of the road first
Before you schedule the first skip-level, say this out loud to your managers and to the people you’ll meet:
Skip-levels are for pattern detection and support, not secret scorecards on the managers in the middle. Afterward, you will share themes with managers, not quotes or named stories, unless someone asks you to escalate a serious issue through the proper channel.
Without that contract, people either perform or triangulate. With it, you can ask harder questions and still keep the org’s trust.
Also set expectations with middle managers first: why you’re doing them, cadence and who you’ll meet, what you will and won’t share back, that you won’t assign work or reverse decisions in the room, and topics they want you to listen for.
If managers only hear about skip-levels from their directs after the fact, the ritual starts as a threat. Brief them early, then keep the confidentiality promise.
When skip-levels help vs. when they undermine
Helpful when you’re new or inherited a team and need ground truth (see also first 90 days as a new director), strategy changed and you need to know what people heard, delivery slips while status looks green, or you’re checking whether managers have air cover and clarity.
Undermining when you collect dirt, reverse decisions from one chat, quote people to their boss, only meet the loudest voices, or treat every complaint as an order for the middle manager.
Use skip-levels for system insight and support, not as an end-run around day-to-day managers. If the issue is the manager relationship, use coaching, HR, or a clear performance conversation.
How often should skip-levels happen?
There is no universal cadence. A workable default: a few skip-levels per month on a rotation, denser for 60-90 days after onboarding or a big change, lighter when 1:1s are strong.
Meet everyone once a year with no follow-through and you get theater. Meet the same three people weekly and you get a shadow staff. Aim for a fair sample and predictable follow-through.
Leader prep and a simple skip-level agenda
Prep is short. Re-read recent goals and known risks. Ask the manager offline what they’re proud of and what to listen for. Pick 5-7 questions. Protect confidentiality language in your opening.
Opening script (purpose and confidentiality)
Thanks for making time. I do skip-levels to learn patterns across the team and to see where I can support better. This is not a performance review of you or of your manager. I’ll share themes with managers afterward without names or quotes, unless you ask me to escalate something serious through the right channel. You don’t need a deck. What’s useful for me is what’s working, what’s stuck, and what would help.
Then shut up and let them talk.
Leader skip-level agenda + question bank
0-3 min: Purpose, confidentiality limits, invite their agenda
3-20 min: Their topics first, then your questions
20-27 min: Patterns / support asks / what should I stop or start doing above you
27-30 min: Anything you want me to take away; how (if at all) to follow up
Question bank (pick a few):
- What’s going well that leaders might not see?
- Where do priorities feel clear vs. foggy?
- What slows good work here (process, tools, decisions, handoffs)?
- When do you get stuck waiting on a decision, and from whom?
- What does your manager do that helps most?
- What support does your manager need more of from my level?
- What’s one thing we should stop doing as a leadership team?
- If you had a magic wand for the next 30 days, what would you change?
- How are remote or hybrid norms helping or hurting collaboration?
- What should I be worried about that isn’t on a dashboard?
Ask for examples and patterns, not gossip. “Walk me through the last time that happened” beats “Who is the problem?”
Psychological safety without fake intimacy
People tell the truth when the risk feels manageable. Keep the opening promise. Don’t punish candor later. Thank specifics without fishing for names. End with what they want you to do with the information.
If someone freezes: “Want to start with what’s working, then one friction point?” If they only praise: “Where do people get stuck here, even when everyone is trying?”
Remote skip-levels need the same contract, a shared agenda doc, no surprise recording, and patience with silence on video.
What an IC should prepare (and avoid)
You’re not auditioning. You’re giving clean signal.
Prep sheet for ICs
1. Two things going well (with a concrete example each)
2. One friction that blocks the team (system, not personality essay)
3. One ask of senior leadership (decision, clarity, resource, air cover)
4. One thing your manager already knows (so you’re not blindsiding them on routine issues)
5. Optional: a question you want to ask upward
Bring notes, not a pitch deck. For sharper upward 1:1 habits, see how to run a 1:1. If meeting culture is the real pain, see how to run effective meetings.
Say: “Here’s a pattern I’ve seen on three projects…” or “Decisions on X take two weeks because Y; a clearer owner would help.”
Avoid: surprise personal attacks about routine friction, absolute claims you can’t support (“everyone hates…”), negotiating your raise while skipping your manager, or performing only good news.
If the real issue is your manager, be factual and proportional. Describe behaviors and impact. Say whether you’ve raised it with them. Ask how the leader prefers serious concerns handled.
Handling complaints about a direct manager
Listen fully. Separate pattern or system issues from individual conduct. Ask what they’ve already tried and what outcome they want. State what you can do: share themes, coach the manager, or escalate if needed. Do not promise secrecy you can’t keep if the issue requires HR action.
Serious issues (harassment, discrimination, safety, retaliation, illegal conduct, clear policy violations) are not “skip-level themes.” Those need your company’s reporting path and HR. This is not legal advice. Point people to policy and People Ops when the topic crosses that line.
How to share insights back without breaking trust
After a round of skip-levels, synthesize. Don’t forward transcripts.
Theme synthesis note to managers (no attribution)
Skip-level themes (date range): [Team / org]
Purpose reminder: pattern detection + support; no individual quotes.
What I’m hearing works:
- Theme 1 (2-3 plain sentences)
- Theme 2
Friction / risk themes:
- Theme 1 + example type (not person)
- Theme 2
Asks of my level (director/VP):
- Decision / clarity / resource / process change
What I will do:
- [Your commitments and timing]
What I’m asking managers to consider:
- [Optional, non-accusatory prompts]
Open questions / need your context:
- …
Share themes in a managers’ forum or 1:1. Invite their context. Then act on what only you can fix above them. If nothing changes after skip-levels, people learn the ritual is theater and stop telling the truth.
Skip-levels vs. open office hours
| Skip-level | Open office hours | |
|---|---|---|
| Who initiates | Leader samples people | Anyone drops in |
| Sample quality | Designed rotation | Self-selected |
| Best for | Patterns across the org | Quick unblock / access |
| Risk | Feels like audit if mishandled | Only confident people show up |
Use both if you want. Don’t pretend office hours replace a skip-level sample, and don’t pretend a skip-level replaces coaching your managers.
Common skip-level failure modes
Skipping the rules of the road. Quoting people to their managers. Only meeting favorites or critics. Assigning work that cuts out the manager. Collecting input with no loop back. Turning every session into status. Using skip-levels instead of coaching managers directly. Treating one story as a company-wide fact.
Fix it with clear purpose, a fair sample, theme-only feedback, and visible follow-through.
FAQ
What should I say in a skip level with my boss’s boss?
Lead with what’s working, one concrete friction, and one clear ask of leadership. Keep manager critique factual and tied to impact. You don’t need to fill every silence.
How do manager skip level best practices differ from IC prep?
Managers being skipped over need the upfront contract and the theme readout. ICs need a short prep sheet and restraint on politics. Leaders own the safety of the format.
Are skip-level meeting questions supposed to include career talk?
A little is fine if the person raises it. Don’t turn a pattern-detection skip-level into a full career committee. Point career depth back to their manager and a proper development 1:1.
What if my company has no formal skip-level meeting purpose written down?
Write a three-line charter anyway: why, confidentiality limits, how themes return to managers. Informal orgs still need the contract.
A skip level meeting works when everyone knows the job: detect patterns, support the system, protect people from triangulation. Announce the rules, ask better questions, share themes not quotes, and fix what only you can fix. Do that, and skip-levels stop feeling like a trap and start feeling like leadership with the lights on.