Skip-Level Meetings: A Practical Guide for Small Companies

A skip-level meeting is simple in concept — a leader talking directly with someone below their direct reports — and surprisingly easy to run in a way that quietly damages the manager relationship it's supposed to complement, not replace.

What it's actually for

Real visibility below the layer a leader normally sees. Information naturally filters and softens as it moves up a hierarchy, not through anyone's dishonesty, but because each layer summarizes and prioritizes what seems most relevant to pass along. A skip-level gets a leader closer to the unfiltered, current reality of what's happening on the ground.

Catching a problem before it's fully escalated. Someone might mention something in a skip-level that hasn't yet reached their manager, or that they haven't found the right moment to raise — not because they're going around their manager, but because the conversation naturally invited it.

Genuine development and recognition for someone the leader might otherwise rarely interact with directly. For a promising employee two levels down, a skip-level can be a meaningful, motivating signal that their work is visible beyond their immediate manager.

Why managers often feel threatened by them, and when that's warranted

The instinctive worry — "is this about me, is my report about to complain about me, will this undermine my authority" — is understandable, and occasionally justified if skip-levels are run poorly: conducted in secret, used to relay directives that bypass the manager, or treated as an opportunity to fish for complaints. Run this way, the worry is completely warranted, and the practice deserves the resistance it gets.

Run well, a skip-level doesn't need to threaten the manager relationship at all — it's a complement to it, not competition for it.

How to run one without undermining the manager

Tell managers this is happening, as standard practice, not a targeted signal. "I do quarterly skip-levels with everyone's teams" is a fundamentally different message than a skip-level that only happens once, right after a manager did something a leader is concerned about — the latter reads, correctly, as an investigation rather than a normal practice.

Keep the conversation forward-looking and general, not a complaint-collection session. Questions like "what's going well, what's frustrating, what would help you do your job better" invite honest input without specifically fishing for manager criticism.

Don't relay directives through a skip-level that should go through the actual manager. If something needs to change about how a team operates, that conversation belongs with the manager, not delivered as an instruction to their report in a skip-level, which genuinely does undermine the manager's authority regardless of intent.

If something concerning does surface about the manager, take it to the manager directly (with appropriate care about confidentiality) rather than acting unilaterally based on one skip-level conversation. The same pattern that applies to any single data point applies here — one conversation is a signal worth exploring further, not a verdict to act on alone.

Questions that work well in a skip-level

• What's the most useful thing your manager does for you day to day?
• Is there anything blocking your work that hasn't been resolved yet?
• What's something you wish leadership understood better about your team's day-to-day?
• Is there anything about how decisions get made around here that's confusing or frustrating?
• What would make the biggest difference to your work in the next few months?

None of these directly probe for manager criticism, which is deliberate — genuine concerns about a manager, if real, tend to surface naturally within an honest, open conversation without needing to be solicited directly.

Cadence and scale

Quarterly is a reasonable default for a small company — frequent enough to maintain real, current visibility, infrequent enough that it doesn't function as a competing, more-frequent reporting relationship that quietly erodes the actual manager's role. At very small scale (under roughly thirty people), a leader might reasonably have some form of direct contact with almost everyone already, making formal skip-levels less necessary as a distinct practice — the value increases specifically once the organization has grown past the point where that natural, informal contact still happens on its own.

What to do with what you learn

Information from a skip-level should generally flow back into the organization through normal channels, not become a private data point the leader quietly acts on alone. If a genuine, actionable theme emerges — a process that's consistently frustrating across several skip-levels, a resource gap nobody had flagged upward yet — raising it with the relevant managers directly, crediting the source generally rather than attributing it to one specific report, keeps the practice from feeling like a channel for anonymous reporting on individuals.

This distinction matters most when the same concern surfaces from several different people independently. A single mention is a data point worth holding loosely; the same concern raised, unprompted, across multiple skip-levels with different people on different teams is a much stronger signal that something systemic deserves direct attention — and it's a pattern that's genuinely difficult to see from anywhere except this specific vantage point, which is part of what makes the practice valuable despite the real care it requires to run well.

What a new leader should know before starting these

A leader new to a company or a larger role should be especially careful in their first few rounds of skip-levels, since people are often reading these early conversations for signals about what kind of leader they're dealing with — whether information shared candidly will be used constructively or held against the manager in between. Being explicit, from the very first skip-level, about how the practice works and what it isn't for sets a tone that makes every subsequent conversation more genuinely useful.

The short version

A skip-level meeting is a genuine tool for real visibility and for developing people a leader wouldn't otherwise interact with directly — and it stays a healthy tool only when it's run transparently, as standard practice rather than a targeted investigation, and kept focused on the employee's own experience rather than fishing for complaints about their manager. Run this way, it complements the manager relationship instead of quietly competing with it, and it earns its place on the calendar by producing real visibility rather than becoming a scheduled formality nobody quite remembers the purpose of.