What is a skip-level meeting, and how do you run one without undermining managers?

A skip-level meeting is a structured conversation between an employee and their manager's manager—often a skip-level 1 on 1—designed for executive listening, not decision-by-proxy. Done well, it surfaces systemic issues and career context without bypassing the direct manager who owns team execution and feedback day to day.

Why do organizations run skip-level meetings?

Every layer of management filters signal. That is not malice; it is bandwidth, framing, and the natural urge to shield leaders from noise. The problem appears when the filter becomes a dam: engineers stop raising cross-team blockers, managers hide bad news to look competent, and executives operate on polished narratives instead of ground truth.

Skip-level meetings restore a controlled bypass—not around accountability, but around information asymmetry. Google's research on manager quality (often summarized as Project Oxygen) reinforces that frontline managers shape experience more than almost any policy deck. Skip-levels do not replace those managers; they help senior leaders see whether manager systems, staffing, and priorities actually match what ICs experience.

The payoff shows up in three places: earlier detection of attrition risk, faster correction of broken processes that no single team can fix, and stronger psychological safety when people believe someone above their chain will hear them without retaliation. The cost of getting skip-levels wrong is equally real: managers feel surveilled, employees learn that going over someone's head is rewarded, and trust collapses faster than any all-hands can rebuild it.

What is the difference between a skip-level meeting and going around your boss?

Going around your boss is ad hoc, often emotional, and usually tied to a specific conflict. A skip level meeting is scheduled, bounded, and governed by explicit norms. The skip-level leader listens; they do not reassign work, rewrite roadmaps, or contradict the manager in the moment unless there is a safety or compliance issue that cannot wait.

Think of the direct manager as the operating system and the skip-level leader as diagnostics. Diagnostics can reveal kernel panics; they should not reinstall the OS during standup. When executives confuse the two roles, they train teams to treat skip-levels as appeal courts—which destroys manager authority and turns every disagreement into politics.

Who should run skip-level 1 on 1s in engineering?

In most product-engineering orgs, skip-levels are owned by the director or VP who owns the manager chain. Staff-plus engineers sometimes run technical skip-levels for architecture or platform pain, but those are supplementals, not replacements for people leadership skip-levels. Peers skip-leveling each other's reports is almost always a mistake unless HR and both managers explicitly design a joint listening program.

Size matters. Below roughly twenty reports in a subtree, a leader can still know names and contexts; above that, skip-levels must be sampled and themed (onboarding, on-call load, promotion clarity) or they become shallow speed dating. Pair quantitative pulses with conversations so you are not only hearing from the most articulate volunteers.

How do you prepare managers so skip-levels build trust instead of fear?

Preparation is the difference between executive listening and executive ambush. At least two weeks before a skip-level cycle, communicate purpose, cadence, and boundaries to all managers in the subtree. Share a one-page leader guide: what you will ask, what you will not do in the room, and how follow-up works.

1. Co-design the agenda with managers. Ask what themes they already hear and where blind spots might be. This signals partnership, not investigation.
2. Offer opt-in context, not surveillance. Managers may share team goals or recent changes; they should not receive a script of what each report will say.
3. Debrief managers on patterns, not betrayals. After each block of conversations, hold a manager forum: "Three teams mentioned unclear promotion bars; two mentioned on-call load." Avoid naming individuals unless there is a agreed escalation.
4. Close the loop publicly. When action follows listening—staffing a platform team, fixing a broken approval workflow—credit the channel and the managers implementing change.

Managers who feel like partners will coach reports to use skip-levels honestly instead of warning them to stay silent. That coaching is itself a marker of mature leadership.

What questions work in a skip-level 1 on 1?

Open-ended prompts beat satisfaction scores in skip-level settings. You are not running a survey; you are building a narrative. Rotate focus areas so repeat conversations do not feel like copy-paste.

• Clarity: "What feels unclear about priorities or success criteria on your team right now?"
• Friction: "Where do you lose the most time to process, tools, or dependencies outside your team?"
• Growth: "What skill or scope do you want six months from now, and what is in the way?"
• Safety: "When was the last time you pushed back on a decision? What happened afterward?"
• Manager support: "What does your manager do that helps you most? What would help more?"

Notice the last item: you are evaluating the system, not recruiting complaints. If serious manager concerns emerge, shift to your HR-partnered escalation path rather than improvising discipline in the skip-level room.

How should skip-level meetings compare to regular 1 on 1s?

Regular 1 on 1s owned by the direct manager handle coaching, feedback, workload, and career progression week to week. Skip-levels operate at a longer wavelength: strategy alignment, organizational barriers, and culture signals. The two formats should reinforce each other, not compete for the same airtime.

If your skip-level conversations repeatedly reopen decisions that belong in the weekly 1 on 1, that is a sign either managers lack authority or skip-level leaders are overstepping. Fix the role clarity before scheduling another round.

How do you run skip-level meetings without undermining managers?

Undermining is a behavior pattern, not a calendar invite. It happens when skip-level leaders contradict managers in public, assign work directly to ICs, or share sensitive feedback without closure. Prevent it with a simple operating contract visible to everyone in the subtree.

1. Default to the manager for execution. End every skip-level with: "Your manager owns day-to-day priorities; I'll partner with them on anything organizational."
2. Never surprise-discipline. Performance issues discovered in skip-levels route to HR and the manager; do not hint at ratings in the conversation.
3. Protect confidentiality with limits. Explain that illegal harassment or safety issues cannot stay confidential; everything else is handled as themes unless the employee wants escalation.
4. Measure manager experience too. Short pulse: "Skip-levels this quarter helped me lead better" gives you a check on whether the program strengthens the chain or weakens it.
5. Document actions, not transcripts. A shared log of systemic commitments beats Slack summaries that feel like surveillance files.

When managers see skip-levels improving their tooling, staffing, and clarity, they become advocates. When they see them as secret tribunals, they become gatekeepers—and your best source of truth goes quiet.

What does good follow-up look like after skip-level listening?

Executive listening without follow-up is worse than no listening at all. Employees remember whether anything changed after they risked candor. Within thirty days of a skip-level cycle, publish a brief "You said / We did" note at the org or department level: three themes, three actions, one thing still in progress with an owner and date.

Tie actions to mechanisms managers already use: clearer leveling docs reviewed in 1 on 1s, on-call policy tweaks, dependency SLAs with partner teams. Avoid hero projects that only the VP can see—those teach ICs that bypassing the manager is the fast path.

For engineering leaders building muscle in both skip-levels and weekly 1 on 1s, consistency beats charisma. A predictable rhythm of listen, aggregate, act, and report back turns skip-level meetings from a anxiety event into part of how the org learns.

Frequently asked questions

Related: Google Project Oxygen: what it found about managers (and why it still matters), Beyond the title: 5 truths about leading high performance teams, High impact engineering 1:1: a framework for elite leadership.

Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.