How to Run a Skip-Level: A Practical Guide for Engineering Managers

Published May 23, 2026 · Updated July 19, 2026

A skip-level meeting — a manager meeting with someone two or more levels below them, without the direct manager in the room — is one of the highest-leverage and easiest-to-botch tools in engineering leadership.

Done well, it surfaces problems weeks before they'd otherwise reach you, and signals that the organization has more than one channel for feedback to travel through. Done badly, it reads as going around someone's manager, and the anxiety it creates outweighs anything useful it surfaces.

The difference is almost entirely about how deliberately you frame the purpose and how visibly you follow up.

Why Skip-Levels Go Wrong

The failure mode isn't usually a bad question — it's an unclear purpose. If a report walks in unsure why a skip-level manager suddenly wants 30 minutes with them, they'll default to caution: careful, safe answers, no real signal.

The two most common causes:

  • The direct manager was surprised by it. If a report finds out their manager wasn't told, or wasn't asked first, the meeting immediately looks like it's about the manager, not about the report's growth or blockers.
  • Nothing ever visibly changes afterward. If a report raises something real once and nothing changes, they'll assume the meeting is theater the next time — and stop bothering.

Both are avoidable with a bit of structure.

1. Set the Expectation With the Manager First

Talk to the direct manager before scheduling anything. Explain the purpose plainly: this is about org health and the report's growth, not a performance audit, and not a channel around them. Ask if there's anything specific worth being aware of going in.

This single step prevents most of the anxiety skip-levels create — for both the manager and the report.

2. Open With a Clear Purpose Statement

Start the meeting by saying, out loud, what it's for. Something close to: "This isn't a performance review, and nothing you say here gets used against you or reported back verbatim. I want to understand how things are actually going, hear about blockers I might not see from where I sit, and get a read on team health. [Manager] knows we're meeting."

That last sentence matters more than it seems — it removes the "is this happening behind someone's back" question before it can form.

3. Use a Real Question Bank, Not Generic Small Talk

Vague questions get vague answers. Specific, low-pressure questions get real ones. A few that consistently work well:

  • "What's something that's harder than it should be right now?"
  • "Is there anything blocking you that your manager might not have full visibility into?"
  • "What's one thing about how the team works that you'd change if you could?"
  • "Do you feel like you know what's expected of you, and how you're doing against it?"
  • "Is there anything you've wanted to bring up but haven't found the right moment for?"

Pick two or three per session — this isn't an interrogation. Leave room for silence; the best answers often come after a pause, not immediately.

4. Keep It Short and Focused

20-30 minutes is enough. A tight structure — purpose statement, two topics from the report, one closing question about anything blocking them — keeps the meeting from feeling like it's fishing for something specific.

5. Capture and Share Action Items — Visibly

Log anything actionable immediately, in the moment, not from memory afterward. If you say you'll follow up on something, that follow-up has to actually be visible later, or the next skip-level starts from a trust deficit instead of a clean slate.

6. Follow Up With the Manager, Not Just the Report

After the skip-level, summarize themes — not verbatim quotes — with the direct manager and agree on what, if anything, changes as a result. This is what turns a skip-level into a genuine feedback loop instead of a one-off vent session that goes nowhere. Never relay a report's exact words back to their manager without asking first; paraphrased themes protect the person who spoke up.

How Accordia Helps

A low-prep visual agenda template for skip-levels means you can build the purpose statement, question set, and action-item checklist in under two minutes, and Slideshow Mode keeps a short, structured meeting from sprawling into an unstructured one. Action items captured during the session sync automatically, so "I'll follow up on that" is a tracked commitment, not a note that gets lost.

Frequently Asked Questions

How often should skip-levels happen?

Quarterly is a reasonable default for a stable team. Monthly can work for larger orgs where a skip-level manager has limited direct visibility.

Should the direct manager know a skip-level happened?

Yes, always. The manager should know it's happening in advance and should hear a summary of themes afterward.

What if the report doesn't say anything useful?

That's normal for a first skip-level. Trust builds over repeated sessions where nothing said ever visibly backfires on them.

Related Guides

Fix your 1-on-1s today.

No credit card required. Free forever for up to 3 reports.
Or try the live demo without signing up.