How do you coach a rep to improve one skill at a time?
PULSEKNOWLEDGE LIBRARY
Coach one skill at a time by diagnosing whether the gap is truly a skill problem, then picking the single highest-leverage skill and running a tight 10/20/30 cadence — teach, drill, then let it show up unprompted — before moving on. This lets a rep improve one measurable behavior in RevOps without diluting focus across ten competing changes.
What it is and why it matters
Single-skill coaching is a discipline, not a preference. A manager who reviews a call and pulls out five things the rep did wrong is doing feedback, not coaching — feedback tells the rep what happened, coaching changes what happens next, and a human brain can only hold one new behavior in working memory while live on a call. The practice of coaching one skill at a time means a manager deliberately suppresses every observation except the single highest-leverage one, for a fixed window, until that one behavior becomes automatic.
The reason this matters starts with diagnosis, not skill selection. Reps underperform for four distinct reasons and only one of them is fixed by coaching: skill (they've been shown the behavior but can't execute it consistently under pressure), knowledge (they've never actually been taught the behavior — a training gap, not a coaching gap), will (they're capable but disengaged, which coaching cannot fix and which usually needs a manager conversation about motivation or a performance plan), and system (their pipeline, territory, or comp plan is broken, and no amount of individual skill-building overcomes bad inputs). Coaching a will problem or a system problem as if it were a skill problem is the single most common reason coaching plans fail — the manager runs drills for a month, nothing changes, and the conclusion drawn is "coaching doesn't work" when the real conclusion is "this was never a skill gap."

Once the gap is confirmed as a genuine skill issue, the next problem is picking which skill. Most reps have more than one weakness, and managers default to whichever one annoyed them on the last call they listened to — which is recency bias, not prioritization. A better method is the Impact-Effort-Frequency matrix: list every skill gap observed across the last five to ten calls, then score each on a 1–10 scale for how much it would move deal outcomes if fixed (impact), how hard it is for the rep to adopt (effort — inverted, since low effort is easier to land), and how often the situation actually comes up in a normal week (frequency). Multiply the three scores. A discovery gap scoring impact 9, effort 5, frequency 10 produces 450; an objection-handling gap scoring 7, 8, 6 produces 336. The higher product wins, because it captures both how much the fix matters and how often the rep gets a chance to practice it live. A closing-technique gap that only surfaces two or three times a month will always lose to a discovery gap the rep touches on every single call, even if the closing gap looks more dramatic in isolation.
This matters specifically inside a RevOps operating rhythm because coaching capacity is a scarce, measurable resource. A frontline manager typically runs six to eight 1:1s a week; if each 1:1 tries to cover a full call-scorecard's worth of feedback, the manager spends coaching time generating a list the rep can't act on, and the org gets a slow bleed of coaching hours that produce no measurable skill movement. Single-skill focus turns each 1:1 into a unit of behavior change instead of a unit of review.

The step-by-step process (mermaid)
The coaching conversation itself follows the GROW model — Goal, Reality, Options, Will — compressed into a single 1:1, and every step is built to land on one skill the rep co-owns rather than one the manager imposed.
Goal. Open by framing the constraint out loud: "For the next few weeks I want us to work on just one thing, not your whole game. If we picked the single skill that would unlock the most deals for you right now, what would it be?" Let the rep answer first — ownership matters more than manager accuracy here. If they name something reasonable, take it. If they don't, steer with evidence rather than opinion: "I'd actually put my attention on discovery. On your last three calls you moved to the demo before we understood why the buyer would act. Can that be our one thing?"

Reality. Anchor the gap to a real, recent call rather than a general impression. Pull a recorded call from a conversation-intelligence tool like Gong or Chorus and play 60–90 seconds of the exact moment. "Listen to this stretch — where could you have asked one more question before moving on?" A specific clip beats an abstract description every time, because the rep can hear the gap instead of having to take the manager's word for it.
Options. Ask the rep to generate the fix rather than supplying it. "What would you do differently on the next call to slow this down?" If they're stuck, offer exactly two choices and let them pick, so the solution still feels theirs: "You could open with a problem question, or mirror their last sentence back. Which feels more natural to you?" Resisting the urge to hand over the answer is the single hardest discipline in this whole process for most managers, because it's slower in the room and faster over the following month.

Will. Close on one observable, gradeable commitment: "This week, on every first call, ask at least three layered discovery questions before any product talk. I'll listen to two calls Friday and grade only that." If a second skill gap surfaces during the conversation, write it down for next month and let it go — reopening scope in the same 1:1 undoes the entire point of the exercise.
Every arrow in that loop matters, but the one managers cut first under time pressure is the weekly leading-indicator check — and it's the one that turns coaching from a vibe into a measured process.

Costs, timelines, and typical ranges
Single-skill coaching runs on a 10/20/30 cadence: three ten-day phases stacked inside a single coaching window, with a clear checkpoint at each mark.
Days 1–10 (Install). Teach the skill explicitly and show a model call — don't assume the rep already knows what "good" looks like just because they've heard the term before. Agree on the one leading metric you'll track. Run two short call reviews in this window, both graded on the target skill only; everything else observed on those calls gets ignored on purpose.

Days 11–20 (Practice). This is the highest-cost phase in manager time: weekly role-play plus live-call grading, roughly 15–20 minutes per 1:1 dedicated specifically to the skill block. Catch the rep doing it right in a real call and name it out loud — positive reinforcement compounds faster here than correction does, because it tells the rep's brain "keep doing exactly that" instead of just "stop doing the other thing."
Days 21–30 (Prove). The behavior should start appearing unprompted, without the rep consciously reaching for it. Confirm the leading indicator has moved and held for at least two consecutive weeks before declaring the skill "stuck" and picking the next one.

Inside that cadence, the individual coaching touchpoint is a 15-minute skill block layered onto the existing 1:1, not a separate meeting: minutes 1–3 for recall and modeling (the rep restates the skill in their own words, then watches or hears a short clip of it done well); minutes 4–8 for deliberate practice via live role-play, where the manager only interrupts if the rep breaks the specific skill rule; minutes 9–12 for feedback limited to exactly one positive observation and one adjustment, never a list; minutes 13–15 for real-world transfer, where the rep names the next three calls on their calendar and one specific trigger moment that will remind them to use the skill live.
On the measurement side, typical leading-indicator targets look like this: discovery-question depth aims for roughly a 30% increase in follow-up questions per call by week two; objection-handling-framework compliance aims for around 80% by week three; call-opening efficiency aims to cut time-to-stated-purpose from something like 90 seconds down under 30. These are directional targets to calibrate against, not universal benchmarks — the actual number depends on the rep's starting baseline, which is why the Reality step in the GROW conversation has to establish a real starting point before any target is set. Review the indicator in a five-minute weekly check-in separate from the full 1:1, so it doesn't get crowded out by pipeline discussion.

Where teams get it wrong
- Coaching ten things at once. A fully loaded call-review checklist feels rigorous but produces no change, because the rep can't hold ten corrections in working memory while live on a call. One skill, one window.
- Coaching the deal instead of the rep. Rescuing this quarter's specific deal is firefighting, not development. Both are legitimate manager activities, but conflating them means the rep never actually improves — the manager just keeps rescuing the same gap deal after deal.
- No follow-through. Naming a skill in one 1:1 and never grading it again teaches the rep that coaching is theater. The weekly leading-indicator check exists specifically to prevent this.
- Rescuing the rep during role-play. Handing over the answer when the rep gets stuck feels helpful in the moment and prevents the actual learning — struggle inside the Options step of GROW is where the behavior gets encoded, not skipped past.
- Applying the same skill focus to every rep. The "one skill" is rep-specific by design. A new SDR's opener gap and a senior closer's multithreading gap are not interchangeable, and running identical drills across a whole team defeats the diagnosis step entirely.
- Switching skills before the behavior sticks. Moving to a new focus before the leading indicator has held for two to three weeks resets the rep back to zero on the first skill, because the behavior was still consciously effortful rather than automatic.
- Treating a will or system problem as a skill problem. If the leading indicator refuses to move for three full weeks despite consistent practice, the diagnosis was probably wrong — re-run the skill/will/knowledge/system split before adding more drills.
Decision framework: when to choose what (mermaid)
Not every underperforming rep needs the same intervention, and applying single-skill coaching to a will or system problem wastes a coaching cycle without fixing anything. Use this decision tree before committing a coaching window to a rep.

Once the tree confirms a genuine skill gap, the choice of cadence intensity depends on rep tenure and role. A brand-new SDR usually needs the full 10/20/30 window because the behavior is being built from scratch; a tenured rep relearning a skill they've lost under pressure often compresses to a shorter window because the neural pathway already exists and just needs reinforcement. For an early-cycle rep the highest-leverage skill is almost always discovery or pre-call planning, since it gates everything downstream. For a closer, it's typically multithreading or negotiation — skills that show up less often per call but carry outsized deal impact. For an SDR, it's the opener and the first objection turn, since those two moments decide whether a call continues at all. Matching the skill choice to the role, and the cadence length to the rep's starting point, is what keeps the framework from becoming a one-size-fits-all script.
Related questions
How do you diagnose whether a rep's problem is skill, will, knowledge, or system?
Check whether they've ever demonstrated the behavior under easy conditions (knowledge), do it inconsistently under pressure (skill), have healthy pipeline but aren't trying (will), or have healthy effort but broken inputs (system). Each needs a different fix — only skill gaps respond to coaching.
How do you pick which skill to coach first when a rep has several weaknesses?
Score each gap on Impact, Effort, and Frequency from 1–10 and multiply. The highest product is the skill that most often shows up and most changes outcomes when fixed — coach that one first and park the rest.
How long should a single-skill coaching window last?
Roughly 10/20/30 days — teach, practice, then confirm the behavior appears unprompted. If the leading indicator hasn't moved by day 21, re-diagnose before extending the window.
What should a manager measure during single-skill coaching instead of quota?
One leading indicator tied directly to the skill's execution — like follow-up questions per call or framework compliance percentage — not lagging metrics like win rate, which take months to shift and are influenced by far more than the one skill.
FAQ
How long should you stay on one skill before moving to the next? Roughly three to four weeks on the 10/20/30 cadence, or until the leading indicator holds steady unprompted for two to three consecutive weeks. If nothing has moved by week three, re-diagnose rather than extending the same drills.
What if the rep has five obvious weaknesses at once? Rank all five with the Impact-Effort-Frequency matrix and coach only the top-scoring one. List the other four somewhere visible and explicitly park them — trying to fix five simultaneously fixes none of them.
Does focusing on one skill slow down a rep's overall development? No — it speeds it up. Reps change behavior faster when they only have to hold one new habit in working memory during a live call. Spreading attention across many skills at once produces shallow improvement that disappears the moment the call gets stressful.
How do you coach one skill without ignoring a deal that's at risk right now? Separate the two conversations entirely. Run a dedicated deal-coaching session to address the immediate risk, then keep the 1:1 disciplined on the single development skill. Letting deal firefighting hijack every coaching session means the rep never actually improves.
What if the single-skill coaching plan isn't producing any movement? Re-run the skill/will/knowledge/system diagnosis. Persistent no-change after a full practice window usually means it was never a genuine skill gap — it's a motivation issue, a teaching gap, or a territory or comp problem, none of which more role-play can fix.
Can conversation-intelligence tools help with single-skill coaching? Yes — tools like Gong or Chorus can auto-flag one specific behavior, such as talk-time ratio or monologue length, so the manager and rep both track exactly one metric without manually re-listening to every call. Use the tooling to narrow the coaching focus, not to widen the checklist.
Sources
- HBR — The Right Way to Hold People Accountable
- Gong Labs — Sales Coaching Research
- RAIN Group — Sales Coaching Best Practices
- Sales Hacker — How to Coach Your Sales Team
- Sandler — The Role of Sales Coaching
- Winning by Design — Sales Coaching Framework
- SBI — Sales Coaching That Drives Performance
Related on PULSE
- [How do you coach a rep who over-relies on one big deal?](/knowledge/cg0796)
- [How do you frame a question that encourages a struggling rep to self-identify their weakest skill without feeling blamed?](/knowledge/cg0866)
- [What specific questions can I ask during a one-on-one to uncover a sales rep's biggest skill gap?](/knowledge/cg0813)
- [Top 10 questions to identify a sales rep's biggest skill gap](/knowledge/cg0812)
- [What metric do you track most closely in your own performance, and why that one?](/knowledge/cg0946)
- [What is one behavior you noticed in your best-performing deal last month that you haven't replicated in others?](/knowledge/cg0937)
This page will be disappearing soon. Save it to your device for $1 — or read it free while it is here.
@Kory-White- · if Venmo asks, the last 4 of my number are 2012









