The Skip-Level Coaching Reboot — 60-Min Training

What it is and why it matters

A skip-level is a meeting where a second-line leader — a VP or Director of Sales — sits directly with an individual rep who reports to one of their frontline managers. The Reboot treats that meeting not as a person diagnostic but as a system diagnostic, borrowing Andy Grove's framing in *High Output Management*: the one-on-one exists to surface how information, blockers, and Coaching flow through a two-layer org, not to grade the human in the chair.

It matters because most skip-levels quietly damage the very manager they were meant to develop. When a rep starts treating the VP as the "real boss," authority silently transfers upward and the frontline manager is hollowed out — Ben Horowitz makes this exact point in *The Hard Thing About Hard Things*. A skip-level run without a protocol collapses into one of three predictable failure modes. The first is the escape valve: the rep vents, the VP drifts into an HR-proxy role, and trust dies the moment the manager finds out. The second is the performance audit: the VP walks in with the pipeline pulled up and fires gotcha questions. The third is the drive-by pep talk: twenty minutes of "you're crushing it" that extracts zero usable signal.

The Training replaces all three with a single ritual — quarterly, 45 minutes in the room inside a 60-minute calendar block, scheduled with the manager's full knowledge, and governed by a routing protocol. The target audience is VPs and Directors of Sales who manage managers in B2B SaaS across the $25K–$500K ACV band, where each manager typically owns four to eight reps. The goal is to leave the session with a working operating system, not a vibes-based check-in. Structured manager Coaching consistently ranks among the top drivers of rep ramp in revenue-org research, which is what turns a skip-level from "another sales pep talk" into a working session the manager is actually measured against. The word Level in "skip-Level" is literal: you are skipping one management layer, and the entire discipline of this Reboot is making sure that skip does not erode the layer you jumped.

The step-by-step process

The 60-minute Training runs in six timed blocks. Treat the clock as part of the curriculum — VPs who let the frame section run long always shortchange the routing protocol, which is where the program actually lives.

Block 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."* Reframe the meeting to system-diagnostic and name the three failure modes out loud so every VP recognizes the one they personally default to.

Block 2 — When to skip-level, and when not to (0:05–0:20, 15 min). Spend the most time here. Establish the quarterly default and the hard "do not" list. Have each participant write their current cadence; most admit "ad hoc when something breaks," which is itself the diagnosis.

Block 3 — The manager-not-undermined frame (0:20–0:30, 10 min). Install a three-part script every VP repeats verbatim: tell the manager first (48-hour minimum pre-brief), open the rep meeting by anchoring the manager's authority, and close by re-pointing every action back to the manager's next one-on-one. Lara Hogan's *Resilient Management* names the principle: authority that is not visibly reinforced upward is silently transferred upward.

Block 4 — The rep-first agenda (0:30–0:40, 10 min). Drill the in-room agenda: human-first opener, then "walk me through your week, not your pipeline," then one deal deep (rep's choice), then one Coaching gap the rep names themselves, then commitments plus a what-goes-back preview.

Block 5 — Observation stance and routing (0:40–0:55, 15 min). Teach the observation posture — you are a scientist in the room, not a coach — and the four-bucket protocol for classifying everything the rep says before they leave.

Block 6 — Commitments (0:55–1:00, 5 min). Each VP writes one manager to skip-level first, the 48-hour pre-brief date on the calendar, and the first rep. The closing line: *"You will be tempted to skip the pre-brief. Do not. The pre-brief is the program."*

The in-room agenda is fixed at 45 minutes: 0–5 human first, 5–20 their world in their words, 20–30 one deal deep, 30–40 one Coaching gap they name, 40–45 commitments and the what-goes-back preview. Listen across those windows for friction verbs — *waiting, chasing, fighting, guessing, redoing* — because each one marks a system bug the manager may not be able to see from inside a single team. When a rep says "I keep redoing the quote because pricing bounces it back," that is not a rep-effort problem; that is a broken pricing-approval path, and it belongs in bucket one, verbatim, in the manager's next one-on-one.

Costs, timelines, and typical ranges

The Training itself is cheap; the discipline is what costs. Budget one 60-minute live session to install the system, then a recurring per-rep time cost thereafter. With a manager owning six reps and a quarterly cadence, a VP overseeing four such managers runs roughly 24 skip-levels a quarter — about two per week at 45 minutes in the room plus a 15-minute buffer, so plan on two hours of VP calendar weekly once the cadence is fully live. That load is the honest sticker price; VPs who don't reserve it default straight back to ad-hoc.

Cadence ranges to set expectations during the Training:

• Quarterly per rep — the default for B2B SaaS teams of four to eight reps per manager. Frequent enough to catch system drift, rare enough to stay out of the manager's lane.
• Monthly — too frequent; it undermines the manager by turning the VP into a co-manager the rep now escalates to.
• Annually — theater; the rep performs, no signal moves, and the ritual becomes a box-check.
• New-manager exception — one extra skip-level at the 60–90 day mark, so the VP sees the team's reality before the new manager's filter fully sets.

Most rooms already run this inside the standard sales stack, and you should reference tools by name so reps know which dashboard you mean — but pricing shifts constantly, so quote current published rates rather than memory. Broadly: async Coaching and coordination happen in a team-chat tool (a low per-seat monthly line), the session is delivered and recorded over video conferencing (a mid per-seat monthly line), opportunity data lives in the CRM (the largest per-seat line, well into the hundreds per user per month at enterprise tiers), and call-recording / revenue-intelligence platforms add a meaningful per-user annual cost on top. Confirm each vendor's live pricing page before you print a number on a slide — do not anchor a budget conversation to a stale figure.

Two timeline rules protect the program. First, the 48-hour manager pre-brief is non-negotiable and precedes every rep session. Second, the 24-hour post-summary — a three-bullet note to the manager using only the shareable buckets — must go out the same next day while memory is fresh. Miss either window and the ritual degrades back toward the escape-valve failure mode within a single quarter.

Where teams get it wrong

The most common failure is skipping the pre-brief because it feels like overhead. It is not overhead — it *is* the program. Without it, the rep reasonably assumes the manager doesn't know, which reframes the whole meeting as a bypass and re-arms the escape valve.

The second failure is the audit reflex: pulling up the rep's pipeline before walking in. Don't. Look at the numbers afterward, if at all. Arriving with their dashboard open signals interrogation, not observation, and the rep clams up for the full 45 minutes. Walk in with a blank page and a pen.

The third failure is instructing in the room. The moment a VP starts coaching the rep directly, they have implicitly told the rep their manager's Coaching is insufficient. Bite your tongue, write it down, and coach the manager later in the manager's own one-on-one. Three observation prompts keep you in the right posture: *"Tell me more"* (use it six-plus times), *"What would have to be true for that to work?"*, and *"Who else sees what you are seeing?"*

The fourth and most damaging failure is bucket-three leakage — repeating something the rep shared in confidence. The four buckets are: (1) goes back verbatim — system, process, and enablement issues the manager hears word-for-word; (2) goes back as a theme — a pattern across multiple reps, never sourced to one person; (3) stays with you — career thinking, personal context, half-formed thoughts, vaulted forever; (4) routed elsewhere — HR, legal, or comp, which is not the manager's lane. Kim Scott's *Radical Candor* frames the confidentiality break as the betrayal that ends the program; her warning about "ruinous empathy" — being so nice you withhold real signal — is the opposite failure the routing protocol is designed to prevent. Classify every item out loud with the rep before they leave the room so there are no surprises in the summary.

A fifth, quieter failure is scheduling the skip-level as the last meeting of the day. A tired VP does sloppy bucketing, and sloppy bucketing is exactly how bucket-three content leaks into a summary. Block the session mid-day, camera on, calendar held for the full 60 minutes.

Decision framework: when to choose what

Not every impulse to skip-level should become one. The Training teaches a decision gate so VPs route themselves correctly before they ever put time on a rep's calendar.

Run a skip-level when: it's the scheduled quarterly cadence (default); a new manager is 60–90 days in and you need the team's unfiltered reality; a strategic deal is live and you want the rep's read rather than the manager's summary; or you suspect a system problem — pricing, ICP, an enablement gap — that a single manager can't see.

Do not run a skip-level when: the rep has asked for an HR conversation (route to HR, full stop); you are angry at the manager (cool off, do the manager one-on-one first); it's a PIP situation (the manager owns that — you don't parachute in); or you haven't told the manager 48 hours in advance (fix that before anything else). Kim Scott's distinction between caring personally and meddling maps directly here — the cadence is the care, and the protocol is what stops the meddling.

Once you decide to run it, the routing decision inside the room is its own gate: a system, process, or enablement issue goes back verbatim; a cross-rep pattern goes back as an unsourced theme; HR, legal, or comp gets routed the same day; everything else is vaulted. That routing is what converts a friendly chat into a leadership instrument.

Related questions

How is a skip-level different from a normal manager one-on-one?

A manager one-on-one is direct-line Coaching and accountability — the manager owns outcomes. A skip-level is a second-line observation ritual: the VP listens for system-level signal and routes it back through the manager, never replacing the manager's authority or day-to-day direction.

How long should a skip-level meeting actually run?

Block 60 minutes on the calendar but plan 45 in the room, leaving a 15-minute buffer for notes and bucketing while it's fresh. Anything shorter turns into a drive-by; anything longer drifts into audit territory or co-managing.

What do I tell the manager afterward?

Within 24 hours, send a three-bullet summary drawn only from the shareable buckets — verbatim system issues and unsourced cross-rep themes. Never include vaulted personal or career content, and never source a theme to the individual rep who raised it.

Can skip-levels be run remotely over video?

Yes. Keep the camera on, block the full hour, and never schedule it as the last meeting of your day. A tired VP does sloppy routing, which is the fastest path to leaking confidential context into the manager summary.

Who should be trained on this Reboot?

Every VP and Director of Sales who manages managers. Frontline managers don't run skip-levels on their own reports; they receive the pre-brief and the summary, so brief them on the protocol so the cadence reinforces rather than threatens their authority.

FAQ

What if the rep says something terrible about the manager during the skip-level? Do not react in the room. Ask "tell me more" twice, classify the comment into a bucket — usually a verbatim system issue, a cross-rep theme, or HR routing, almost never the vault for a serious concern — and decide afterward whether it's a Coaching conversation with the manager or an HR matter.

How often should skip-levels happen? Quarterly per rep is the default for B2B SaaS teams of four to eight reps per manager. Monthly is too frequent and undermines the manager; annual cadence is theater that produces no usable signal.

Should I pull up the rep's pipeline before the meeting? No. Review it afterward if at all. Walking in with their dashboard open signals an audit rather than observation, and the rep will guard everything they say for the full session.

What if my manager pushes back on the cadence? Show them the protocol — specifically the 48-hour pre-brief and the 24-hour summary. Most resistance evaporates once managers see the program is engineered to reinforce their authority, not erode it.

What if I find something the manager is doing wrong? Bring it to their one-on-one within a week, framed as an observed pattern, never as "the rep told me." If sourcing is genuinely unavoidable, ask the rep's permission before you name them.

How do I stop a skip-level from turning into a Coaching session? Hold the observation stance: you are a scientist, not a coach, while you're in the room. Every time you feel the urge to instruct, write it down instead and carry it to the manager's own one-on-one afterward.

Sources

• https://www.radicalcandor.com/ — Kim Scott, *Radical Candor*: care personally, challenge directly, and the cost of ruinous empathy.
• https://www.harpercollins.com/products/the-hard-thing-about-hard-things-ben-horowitz — Ben Horowitz on protecting frontline manager authority.
• https://www.penguinrandomhouse.com/books/298415/high-output-management-by-andrew-s-grove/ — Andy Grove on managerial leverage and the one-on-one as system diagnostic.
• https://larahogan.me/books/resilient-management/ — Lara Hogan, *Resilient Management*, on visibly reinforcing delegated authority.
• https://review.firstround.com/ — First Round Review operator interviews on operating cadence and skip-levels.
• https://hbr.org/ — Harvard Business Review coverage of effective skip-level meetings.
• https://www.manager-tools.com/ — Manager Tools guidance on running skip-level meetings.
• https://lattice.com/library — Lattice operator resources on quarterly skip-level cadence.
• https://www.15five.com/blog/ — 15Five guides on manager Coaching and skip-level programs.

Related on PULSE

• [The SDR Outbound Calling Coaching Reboot — 60-Min Training](/knowledge/st225)
• [The Ride-Along Coaching Reboot — 60-Min Training](/knowledge/st213)
• [The Sales Coaching Cadence Reboot — 60-Min Training](/knowledge/st189)
• [Overcoming Call Reluctance: Coaching Template for a Weekly Morning Huddle](/knowledge/st0793)
• [Top 10 call coaching role-play scenarios for sales teams](/knowledge/st0568)
• [Top 10 call coaching training drills for B2B sales reps](/knowledge/st0567)