The Skip-Level Coaching Reboot — 60-Min Training

Direct Answer

The skip-level reboot in one breath: Skip-levels are not escape valves, performance audits, or manager bypasses — they are a quarterly observation ritual where the VP sits with a rep for 45 minutes, asks rep-first questions, surfaces system-level blockers, and routes findings back to the manager through a pre-agreed protocol that strengthens (never undermines) the manager's authority.

Run this 60-minute training to install the cadence, the frame, the agenda, and the what-goes-back rules across your front-line managers' teams.

Audience: VPs and Directors of Sales who manage managers in B2B SaaS, $25K-$500K ACV. Goal: Leave the room with a working skip-level operating system — not a vibes-based check-in.

Section 1 — The Reboot Frame (0:00-0:05, 5 min)

Open cold. Put one sentence on the screen: *"Most skip-levels secretly damage the manager you're trying to develop."* Watch the room nod.

Then reframe. Borrowing from Andy Grove's *High Output Management*, a skip-level is a system diagnostic, not a person diagnostic. You are not there to grade the rep or audit the manager. You are there to observe how information, blockers, and coaching are flowing through a two-layer system.

State the three failure modes you are eliminating today:

• The Escape Valve — rep uses skip-level to vent about manager. You become an HR proxy. Manager finds out. Trust dies.
• The Performance Audit — VP arrives with the rep's pipeline pulled up, asks gotcha questions, leaves the rep terrified.
• The Drive-By Pep Talk — 20 minutes of "how's it going, you're crushing it" with zero signal extracted.

Tell the group: "We are replacing all three with one ritual, run quarterly, with a protocol."

Section 2 — When To Skip-Level, And When Not To (0:05-0:20, 15 min)

Spend 15 minutes here because this is where the program lives or dies.

Run a skip-level when:

• It is the scheduled quarterly cadence for every rep on every manager's team (default mode).
• A new manager is 60-90 days in and you need to see the team's reality without filtering.
• A strategic deal is in play and you want to understand the rep's read, not the manager's summary.
• You suspect a system problem (pricing, ICP, enablement gap) that may be invisible to one manager.

Do NOT run a skip-level when:

• The rep has asked for an HR conversation. Route to HR. Period.
• You are mad at the manager. Cool off. Do the manager 1:1 first.
• It is a PIP situation. The manager owns that. You do not parachute in.
• You have not told the manager 48 hours in advance.

Have each participant write down their current cadence. Most will admit it is "ad hoc when something breaks." That is the diagnosis.

Set the new default out loud: "Every rep, every quarter, 45 minutes, scheduled with the manager's knowledge, never without." Kim Scott's *Radical Candor* calls this the difference between caring personally and meddling — the cadence is the care; the protocol is what stops the meddling.

Section 3 — The Manager-Not-Undermined Frame (0:20-0:30, 10 min)

This is the part new VPs skip and live to regret. Ben Horowitz in *The Hard Thing About Hard Things* writes that the fastest way to destroy a frontline manager is to make their reports believe the VP is the real boss. Skip-levels done badly do exactly that.

Install the three-part frame. Make every VP in the room repeat the script verbatim.

Step 1 — Tell the manager first. 48 hours minimum. Script:

*"Hey [Manager], I am running my quarterly skip-level with Priya on Thursday. Standard cadence, not about you, not a performance review. I will send you a 3-bullet summary Friday — what I observed, what I committed to, and one thing I want your read on. Anything you want me to listen for?"*

Step 2 — Open the rep meeting by anchoring the manager's authority. Script:

*"Priya, this is my quarterly time with you. Your manager Marcus knows we are talking — I told him Tuesday. Nothing you say to me bypasses him; if something needs to change in your day-to-day, Marcus is still the person who changes it. I am here to listen to the system, not grade the people."*

Step 3 — Close by re-pointing to the manager. Script:

*"Best next step on the [X] thing is to bring it to Marcus in your next 1:1. If it does not move in two weeks, ping me."*

Lara Hogan's *Resilient Management* nails the underlying principle: authority that is not visibly reinforced upward is silently transferred upward. Your job in a skip-level is to keep authority where it belongs.

Section 4 — The Rep-First Agenda (0:30-0:40, 10 min)

Hand out the 45-minute agenda. Drill it.

• 0-5 min — Human first. "What is going on outside work that I should know about?" Not optional. Not skippable.
• 5-20 min — Their world, their words. "Walk me through your week. Not your pipeline — your week." Listen for friction verbs: *waiting, chasing, fighting, guessing, redoing*. Each one is a system bug.
• 20-30 min — One deal, deep. Rep picks the deal, not you. Ask: *"What do you actually believe will close this?"* Then: *"What does Marcus think? Where do you two see it differently?"*
• 30-40 min — One coaching gap, named by them. "If Marcus could coach you on one thing the next 90 days, what would move the needle most?" This is gold. It tells you what the manager is or is not doing without the rep having to rat.
• 40-45 min — Commitments and the what-goes-back preview. You name what you will tell Marcus. Rep confirms or edits.

First Round Review's interviews with operators like Claire Hughes Johnson make the same point: the agenda is rep-first because the rep is the only person in the room who has not been filtered yet.

Section 5 — Observation Stance + What Goes Back Protocol (0:40-0:55, 15 min)

This is the section that turns a polite chat into a leadership instrument.

Observation, not instruction. You are a scientist, not a coach in this room. If you start instructing, you have just told the rep their manager's coaching is insufficient. Bite your tongue. Write it down. Coach the manager later.

Three observation prompts that always work:

• *"Tell me more."* (Use 6+ times.)
• *"What would have to be true for that to work?"*
• *"Who else sees what you are seeing?"*

The What-Goes-Back Protocol. Before the rep leaves the room, you classify every piece of information into one of four buckets, out loud, with the rep:

1. GOES BACK VERBATIM — system issues, process bugs, enablement gaps. Manager hears it word for word.
2. GOES BACK AS A THEME — pattern across multiple reps; you do not source it to this rep.
3. STAYS WITH YOU — rep's career thinking, personal context, half-formed thoughts. Vault.
4. ROUTED ELSEWHERE — HR, legal, comp committee. Not the manager's lane.

Then, within 24 hours, send the manager a 3-bullet summary using only buckets 1 and 2. Never bucket 3. Ever. Kim Scott calls bucket-3 leakage *"the betrayal that ends the program."*

Section 6 — Commitments and the First Skip-Level (0:55-1:00, 5 min)

Close fast. Each VP in the room writes down:

• One manager whose team they will skip-level first this quarter.
• The 48-hour manager pre-brief date on the calendar before they leave the room.
• The first rep they will sit with.

Tell them: *"You will be tempted to skip the pre-brief. Do not. The pre-brief is the program."*

FAQ

Q: What if the rep says something terrible about the manager during the skip-level? A: You do not react in the room. You ask *"tell me more"* twice, classify it (bucket 1, 2, or 4 — almost never 3 for serious concerns), and decide afterward whether it is a coaching conversation with the manager or an HR routing.

Q: How often should skip-levels happen? A: Quarterly per rep is the default for B2B SaaS teams of 4-8 reps per manager. Monthly is too much (undermines manager); annually is theater.

Q: Should I pull up the rep's pipeline before the meeting? A: No. Look at it after, if at all. Walking in with their dashboard signals audit, not observation.

Q: What if my manager pushes back on the cadence? A: Show them the protocol — especially the 48-hour pre-brief and the 24-hour summary. Most pushback evaporates when managers see the program reinforces their authority, not erodes it.

Q: Can I do skip-levels over Zoom? A: Yes. Camera on, calendar blocked for 60 min (not 45 — leave buffer), and never the last meeting of your day. Tired VP equals sloppy bucketing.

Q: What if I find something the manager is doing wrong? A: Bring it to their 1:1 within a week, framed as observed pattern, never as "Priya told me." If sourcing is unavoidable, ask the rep's permission first.

Sources

• Kim Scott, *Radical Candor*, 2017 — care personally, challenge directly, and the cost of "ruinous empathy."
• Ben Horowitz, *The Hard Thing About Hard Things*, 2014 — protecting frontline manager authority.
• Andy Grove, *High Output Management*, 1983 — managerial leverage and the one-on-one as system diagnostic.
• Lara Hogan, *Resilient Management*, 2019 — visible reinforcement of delegated authority.
• First Round Review, Claire Hughes Johnson interviews on operating cadence and skip-levels.
• Harvard Business Review, "The Skip-Level Meeting Done Right," 2021.
• Manager Tools podcast, "Skip-Level Meetings" series, Mark Horstman and Mike Auzenne.
• Lattice / 15Five operator guides on quarterly skip-level cadence in B2B SaaS revenue orgs.