Skip-Level Circuit How-to: 3 People

Sep 10, 2026 | How-tos, Leading Others

Treat the circuit as pattern detection with a pre-announced contract, not a secret audit of middle managers. The play fails if themes are not shared back (without attribution) or if you collect quotes as ammunition. Three people is intentional scarcity: enough for patterns, too few for a fake org diagnosis.

Deep context: Skip-level meetings. Stage hubs: Director / VP, New Manager. ICs invited into the play can prep from the sheet below and the Individual Contributor hub.

Play card

Field	Detail
Time box	25–30 minutes per conversation; ~2–2.5 hours total including synthesis
Players	Leader; three skip-level participants; middle managers briefed beforehand
Goal	Theme note back to managers (no attribution) + personal follow-ups + escalation flags if needed
Done looks like	Managers hear themes within a week; participants know the contract up front

Optional note-taker: only if trusted and themes-only. Prefer the leader capturing themes personally to avoid quote harvesting.

When to use

New org or new leader listening tour with a bound.
Retention risk signals or engagement noise that needs human texture (not a survey replacement).
Post-reorg listening when reporting lines changed.
Periodic circuit as part of a light operating rhythm (Director / VP hub).

When not to use

Active investigation or ER matter: stop and use proper channels.
Undermining a new manager before they have had time to lead.
Political fishing for quotes to weaponize in a performance case.
Substituting for your own manager 1:1s or for an engagement survey when you need broad measurement.

Choosing three without bias theater

Use a simple roster checklist:

Mix of tenure or roles when possible (not three favorites).
Not only people who already email you.
Not a secret “troublemaker panel.”
Transparent enough that managers understand the sampling idea.

Document why these three in one private line for yourself. Do not announce a fake random science story.

Prep with middle managers (required)

Before invites go out, tell managers the rules of the road:

Purpose: pattern listening, not a shadow performance review of them.
Contract: themes, not attributable quotes, return to managers.
Limits: you will escalate harassment, discrimination, safety, or policy issues through proper channels; you will not promise absolute confidentiality for illegal or harmful reports.
Timing: when themes will come back.

If you skip this prep, you earn distrust you deserve.

Timed steps

Per conversation (25–30 min)
| Minutes | Move |
| — | — |
| 0–3 | Opening script: purpose, limits, theme-not-quotes |
| 3–20 | Questions: support, blockers, clarity, ideas |
| 20–25 | “Anything I should know that I didn’t ask?” |
| 25–30 | Thanks + how themes will be used |

After all three (20–30 min synthesis)
1. List repeating themes (appear in 2+ talks) vs one-offs.
2. Separate actionable team themes from individual career follow-ups.
3. Flag anything that must pause the play and route to HR.
4. Draft the theme note to managers without names or gotcha quotes.
5. Schedule delivery within one week.

Opening script

“Thanks for making time. I’m talking with a few people to hear patterns about how work is going: support, blockers, and clarity. This is not a secret performance review of your manager. I’ll share themes back without attributing quotes. I can’t promise absolute confidentiality if something involves safety, harassment, or other issues that policy requires me to escalate. I won’t use this as ammunition. What questions do you have about that before we start?”

Question bank (use a few; do not interrogate)

Support
– What helps you do your best work right now?
– Where do you need more support than you’re getting?

Blockers
– What slows the team down that leadership could influence?
– What decision is stuck?

Clarity
– What are we optimizing for that still feels fuzzy?
– Where do priorities conflict in practice?

Ideas
– If we could change one operating habit this quarter, what would it be?

Avoid
– “Tell me what’s wrong with your manager” as an opener.
– Leading questions designed to confirm your politics.
– Medical, family, or other inappropriate personal probes.
– Promises you cannot keep (“this never leaves the room” when escalation may be required).

Output artifacts

Theme synthesis note to managers (no attribution):

Skip-level circuit themes: [Date]
Sampling: three skip-level conversations (roles/tenure mix noted without names)
Themes (2+ mentions):
One-offs I’m treating as individual, not org fact:
Follow-ups I own:
Asks for managers:
Escalations (if any): routed via policy/HR; not detailed here

Personal follow-ups (career help, intro, tool access) tracked privately.
Escalation flags handled per company policy, not via this template.

If you are an IC invited in

Prep sheet (10 minutes):

Skim your recent blockers and one improvement idea.
Decide what is theme-safe vs what belongs in HR channels (When to talk to HR vs manager).
You may decline sensitive topics; you are not on trial.
Do not treat the skip-level as a back channel to settle scores.

Circuit vs office hours vs survey

Mode	Strength	Limit
3-person circuit	Depth + bounded patterns	Not statistically broad
Office hours	Open access	Self-selected; easy to miss quiet risk
Engagement survey	Breadth	Thin on mechanism; slow on trust repair

Use the circuit for texture. Do not claim it represents the whole org.

When to pause and route to HR

High-level triggers only (not legal advice): allegations of harassment, discrimination, retaliation, threats, wage/ethics violations, or anything your policy says leave manager listening. Pause the play. Do not investigate freestyle. Point to HR for humans and How HR works for literacy, then follow your company’s process.

Watch-outs

Triangulation: Playing people against their manager.
Quote leakage: “Someone said you…” destroys the contract.
Weaponizing feedback: Themes become ammo in a private war.
Bias sampling: Only allies or only critics.
Fake confidentiality: Over-promising silence.
Skipping the share-back: Listening without return is extraction.