How do you give sales reps feedback they'll actually act on?

What behavioral feedback actually is, and why most of it never lands

Feedback in a sales org is not evaluation. Evaluation is a rating against a standard — a scorecard, a quota attainment number, a mid-year review. Feedback is a description of a specific action and its downstream effect, delivered close enough to the action that the rep can still remember what they were thinking when they did it. Those two things get conflated constantly, and the conflation is why so much of it bounces off. A rep who thinks they're being graded defends. A rep who thinks they're being shown a replay engages.

The mechanical difference is testable. Take any piece of feedback you've given in the last month and ask: could a camera have recorded what I described? "You were nervous on price" — no camera records nervousness. "You stated the number and kept talking for forty seconds" — that's on tape. "You need to be more consultative" — no camera records consultativeness. "You asked three questions in a forty-minute discovery call, all of them closed-ended" — that's countable. The camera test is the single cheapest filter you can run before opening your mouth, and it eliminates most of the feedback that reps ignore, because feedback that fails the camera test is feedback the rep cannot act on even if they want to.

The second failure mode is scope. Managers routinely deliver four or five observations in one sitting because they saved them up for the weekly 1:1. A rep who leaves with five things to fix fixes zero — not from laziness, but because behavior change under live-deal pressure has a working-memory budget of about one item. Under stress on a real call, a rep can consciously run exactly one new pattern. Everything else reverts to habit. So the discipline is brutal triage: of the five things you noticed, which one, if fixed, would move the most deals? Deliver that one. The other four are still true next month.

Third: ownership. There is a large and consistent gap between a fix the manager prescribes and a fix the rep designs. When you say "next time, pause after you state price," the rep hears an instruction and complies at roughly the rate people comply with instructions they didn't choose. When you ask "what could you do differently at that moment?" and the rep says "I think I need to shut up and let them react," it's now their idea, and they defend their own ideas. Same behavior, radically different follow-through. The manager's job is to make the moment visible and then get out of the way while the rep diagnoses it.

Fourth, and the one most often skipped: the loop. Feedback delivered once and never revisited teaches the rep that it wasn't important. If you coach a behavior on Tuesday and never mention it again, you have communicated — accurately, from the rep's point of view — that this was a passing observation. The follow-up is not administrative overhead; it *is* the feedback. A mediocre observation with a scheduled re-check outperforms a brilliant observation with no follow-up, every time.

For RevOps specifically, this matters because coaching quality is one of the few levers that compounds across a whole team without adding headcount. A conversion-rate improvement that comes from a coaching habit persists after the rep changes territories, and it transfers to the next rep the manager hires. That's why RevOps and enablement teams increasingly instrument coaching itself — tracking whether coached behaviors show up on subsequent calls — rather than only instrumenting outcomes.

Diagnose the gap before you open your mouth

Before any feedback conversation, classify what you're actually looking at. Four categories, four completely different responses, and coaching the wrong one is why managers repeat themselves for six months with nothing changing.

Skill gap. The rep knows the behavior is right and cannot execute it yet. They know they should multithread; they don't know how to ask a champion for a CFO introduction without sounding like they're going over the champion's head. This is the only category where feedback plus practice reliably works, and it's the one managers are best at. Response: SBI, role-play, re-observe.

Knowledge gap. The rep would do the right thing if they had the information. They can't answer a security question because nobody gave them the SOC 2 talking points. This looks like a skill gap on a call recording and isn't one. Coaching it as a skill gap insults the rep and wastes both your afternoons. Response: enablement content, a one-page battlecard, a subject-matter expert on the next call — not a coaching conversation.

Will gap. The rep can do it and isn't. This is where most managers over-coach. If a rep executes discovery beautifully on deals they like and phones it in on inbound SMB, that's not a discovery-skill problem. Response: a direct conversation about what's going on — comp, territory perception, burnout, job search, life. More role-play makes it worse because it signals you're not paying attention.

System problem. The rep's behavior is a rational response to a broken environment. Reps skip discovery because marketing's MQLs are so unqualified that discovery is a waste of time, or they discount hard because the comp plan pays the same on a 30% discount. You cannot coach your way out of a comp plan. Response: fix the system, which is a RevOps conversation, not a rep conversation.

A quick diagnostic: does this rep do the desired behavior *anywhere*? If yes, on some deals but not others, it's will or system. If never, on any deal, it's skill or knowledge. Then ask: if I offered them $5,000 to do it correctly on the next call, could they? If yes, it's will. If no, it's skill or knowledge. Crude, but it sorts most cases in thirty seconds and stops you from delivering the wrong kind of feedback.

Also worth checking: is the behavior actually wrong? Managers coach reps toward their own selling style constantly, and a rep with a different but effective style gets coached into mediocrity. Before you flag something, check whether it correlates with worse outcomes for *this* rep, not whether it's how you would have done it. If the rep's win rate on that motion is fine, the "problem" is a preference, and delivering it as feedback burns credibility you'll want later for something real.

The step-by-step process for a session that changes behavior

Here's the full sequence, timed. Total live time: 15–25 minutes. Prep: 10 minutes.

Prep (10 minutes, before the meeting). Pull one call recording. Find one 30–60 second clip. Write the SBI out longhand — literally type the three sentences — because the discipline of writing it exposes any interpretation that snuck in. If your "behavior" sentence contains an adjective about the rep rather than a verb about their action, rewrite it. Decide in advance what the one behavior is. Do not walk in with a list.

Frame (2 minutes). Anchor it to the rep's stated goal, not yours. "You said you wanted your demos to convert better — I pulled a clip from the Brightway call that I think is the lever." If they haven't stated a goal, ask for one before you coach anything; feedback against a goal they never set is a performance review in disguise.

Play the clip and ask first (5 minutes). Play 30–60 seconds. Then: "What do you notice?" Silence. Wait a genuinely uncomfortable amount of time — most managers break at three seconds and fill the gap, which is exactly the same mistake the rep made after stating price. Reps identify their own behavior maybe half the time; when they do, you're done with the hard part.

Deliver SBI if they missed it (2 minutes). Situation: "Twenty-two minutes in, right after the VP asked about pricing." Behavior: "You gave the number, then talked for about forty seconds before they responded." Impact: "We never heard their actual reaction, and the call ended with 'we'll think about it.'" No adjectives. No "you seemed." Stop talking.

Ask the reaction question (2 minutes). "What was going through your head right there?" This single question does more diagnostic work than the rest of the session. "I panicked because I thought the number was too high" is a will/confidence issue and probably a pricing-conviction problem across the whole team. "I always fill silence, I do it everywhere" is a habit. "I was covering because I hadn't validated budget in discovery" is an earlier-stage skill gap, and you're coaching the wrong moment.

Generate options — theirs, not yours (5 minutes). "What are two or three things you could do instead?" Make them produce at least two before you offer anything. If they're stuck after a real pause, offer options as a menu — "some people count to five, some hand the silence back with 'what's your reaction to that?'" — and let them pick. A menu preserves ownership; an instruction destroys it.

Commit and schedule (3 minutes). One behavior, stated by the rep, written down in a shared place. Then the part everyone skips: "Which call this week will you try it on, and when do we listen to it together?" Put the re-check on the calendar before the meeting ends. Forty-eight hours is a good default for a micro-check; the next weekly 1:1 for the full re-listen.

Timelines, cadence, and what this costs in manager hours

The honest cost accounting matters, because coaching programs die when the time isn't budgeted and the manager's calendar wins.

Per session. 10 minutes prep plus 15–25 minutes live, call it 30–35 minutes per rep per week. Managers who skip prep and improvise burn the same live time at a fraction of the effect, because without prep you default to whatever you remember, which is usually the deal and not the skill.

Per manager. A manager with 7 reps running weekly coaching is spending roughly 3.5–4 hours a week on coaching alone, plus the async micro-loops. That's a real chunk of a manager's week, and it's the number to get agreement on before launching a program. A manager with 12 reps cannot run true weekly coaching on all of them — the arithmetic doesn't work — so they either move to biweekly, or they tier: weekly for ramping and struggling reps, biweekly for steady performers, monthly for the top of the board who mostly need stretch work.

Time to visible change. A single specific behavior — pausing after price, asking a second "why," confirming a calendared next step — typically shows up on the next one to three observed calls if the rep owned the fix. If it hasn't appeared after three re-observations, stop re-delivering the same feedback; you've misdiagnosed the category. Composite skills — running genuinely good discovery, multithreading a complex deal — move over 4–8 weeks of repeated reps, not from one conversation.

Ramp horizons for new reps. A rough 30/60/90 that most teams converge on: at 30 days you're coaching mechanics — talk tracks, product accuracy, tooling hygiene. At 60 days you're coaching deal execution — discovery depth, next-step discipline, multithreading. At 90 days the rep drives their own calls and you're refining edges, and coaching shifts from directive to reflective. If you're still coaching 30-day mechanics at day 90, that's a hiring or onboarding signal, not a coaching one.

Cadence that survives contact with a quarter. Weekly 30-minute coaching 1:1, held separately from pipeline review — this is non-negotiable, because when you combine them the deal review eats the coaching every single time, especially in the last three weeks of a quarter. Add a mid-week async micro-loop: two lines in Slack or a comment on the call recording when you catch the rep doing the new behavior. That reinforcement note is disproportionately effective relative to its cost, and it's the piece most managers drop first.

Monthly zoom-out. Once a month, ignore single moments and look at trend across four or five calls plus the leading indicators. One bad call is noise. A pattern across five is a coaching target.

Tooling cost, honestly. Conversation-intelligence platforms — Gong, Chorus, Clari — are per-seat and enterprise-priced; they change the economics by killing the search cost, since finding the coachable moment used to be most of the prep. They don't change the conversation. Teams without a platform can run the identical process off recorded Zoom calls and a shared doc; it costs the manager more prep minutes per session and works fine. Do not let "we don't have Gong" become the reason coaching doesn't happen.

Documentation. One shared running doc per rep — date, behavior coached, what the rep committed to, whether it showed up. Three lines a week. This doc is what makes the loop real, what makes a performance conversation defensible if it ever comes to that, and what lets a new manager inherit a rep without starting from zero.

Where teams get it wrong

Rescuing instead of coaching. The manager jumps on the call and saves the deal. Deal closes, rep learns nothing, and the rep now knows that if things get hard, the manager takes over. Every rescue is a small withdrawal from the rep's development account. Occasionally you have to rescue a deal that's genuinely too big to lose — but count them, and if it's more than rare, the problem is the coverage model.

Coaching the deal instead of the skill. "Send them the ROI deck" fixes one deal. "Here's how you re-engage a champion who's gone quiet" fixes the next forty. Deal advice feels productive because it produces immediate motion, which is exactly why it crowds out skill coaching. A useful test at the end of each session: did the rep leave with something that applies only to this account, or to every account?

The feedback sandwich. Praise, criticism, praise. Reps decode it within two sessions and start bracing every time you compliment them, which poisons your genuine praise. SBI is already non-judgmental — it doesn't need cushioning, because it doesn't attack anyone. Be direct and be kind; those aren't in tension.

Batching feedback for the weekly. You notice something on Tuesday and save it for Friday's 1:1. By Friday the rep doesn't remember the call, the specificity is gone, and you've turned a two-minute async note into a vague conversation. Deliver small things fast and async; save the 1:1 for the one thing that deserves a clip and a role-play.

Same coaching for everyone. Your top performer needs a stretch challenge and probably wants to be coaching others; your ramping rep needs one fundamental drilled to unconsciousness; your struggling veteran needs an honest diagnosis of whether it's will or skill. A uniform program helps none of them, and the top rep in particular will disengage from coaching that's pitched at the middle.

Coaching a system problem with skill feedback. If reps discount because the comp plan doesn't punish discounting, no amount of negotiation role-play fixes it. If discovery is thin because the leads are garbage, coaching discovery is asking reps to work harder at something that doesn't pay. Both are RevOps fixes. Misfiling a system problem as a rep problem is the fastest way to lose a team's trust, because the reps know exactly what the real cause is.

Feedback with no re-observation. The most common failure of all, and the least dramatic. Everything about the session was good, and then nobody ever checked. If you're going to cut one thing from the process, cut prep time before you cut the follow-up.

Only ever coaching problems. Positive feedback should use exactly the same structure and it's wildly underused. "Good call" tells a rep nothing repeatable. "When the CFO pushed back on the number, you reframed to the cost of doing nothing and they re-engaged — do that again" tells them precisely what to repeat. Reps who only hear from you when something's wrong learn to dread the coaching invite.

Timing it badly. Feedback right after a painful loss lands on a rep who's in no state to process it. Wait until the next morning. Feedback in front of peers, even mild feedback, reads as public correction and produces defensiveness out of proportion to the content. Praise publicly, coach privately.

Choosing your response: a decision framework

Not every observation deserves a coaching session. Route by category and by cost of the behavior, or you'll spend your whole week on things that don't matter.

Route by diagnosis first. Skill and knowledge gaps go to feedback and practice. Will gaps go to a candid conversation about what's actually happening — and if the answer is that the rep has checked out, that's a performance-management track, not a coaching track. System problems go to whoever owns the system.

Route by frequency and cost. A behavior that happens on every call and costs you conversion is a coaching target. A one-off in a weird deal probably isn't worth the credibility spend. Managers who flag everything train reps to discount everything they say.

Route by channel. Small, specific, low-emotion observations belong in a two-line async note on the recording, delivered same day. Anything involving pattern, identity, or a hard truth belongs in a live 1:1 with a clip. Anything approaching a performance concern belongs in a scheduled, documented conversation, and probably with a heads-up so the rep isn't ambushed.

Route by rep tenure. Ramping reps get directive coaching — show them the pattern, they'll adopt it. Experienced reps get reflective coaching — ask, let them diagnose, offer a menu at most. Delivering directive coaching to a tenured rep is the fastest way to be tuned out, and delivering pure reflective coaching to a two-week rep leaves them guessing at an answer they have no way to know.

And know when to stop coaching. If you have delivered specific, camera-observable feedback on the same behavior three times, the rep has owned the fix each time, and the behavior still hasn't appeared, the diagnosis was wrong. It is a will or fit issue. Continuing to coach it is kinder in the moment and less kind over a quarter, because it delays a conversation the rep also knows is coming.

Related questions

How long should a coaching 1:1 be?

Fifteen to twenty-five minutes of live time is plenty for one behavior, plus about ten minutes of prep. Longer sessions almost always mean you're covering multiple items, which is the fastest way to get zero of them adopted.

Should coaching be separate from pipeline review?

Yes, and on a separate calendar invite. When combined, deal review consumes the coaching time every quarter-end without exception, because the pipeline is urgent and the skill is merely important.

What if I coach a behavior and the rep's numbers get worse?

Short-term dips are normal while a new behavior is clumsy — that's the awkward middle of skill acquisition. Give it three to four calls. If it's still worse, the behavior may be wrong for that rep's style, so revisit rather than double down.

Can peers give each other feedback effectively?

Yes, and it accelerates learning for the giver more than the receiver. Have two reps swap a recording and deliver SBI to each other. Teaching the standard is how reps internalize it — but keep manager coaching running alongside it.

Do AI tools replace the manager in this loop?

No. Conversation intelligence surfaces the moments, the talk ratios, and the patterns, which kills the search cost. The diagnosis, the ownership, and the follow-up are still human work, and those are the parts that determine whether anything changes.

FAQ

How soon after a call should I give feedback?

Within 24 to 48 hours, while both of you can still recall the moment. Past a week, specificity decays into a vague impression and the rep can't reconstruct what they were thinking. The exception is a painful loss — wait until the next morning, because feedback delivered into raw emotion gets processed as blame.

What's the difference between SBI and the feedback sandwich?

The sandwich hides the message inside praise, so reps learn to brace for the "but" and stop trusting your compliments. SBI states the situation, the observable behavior, and the concrete impact, with no adjectives about the person. It's direct without being an attack, which is why it doesn't need cushioning in the first place.

How do I give feedback to a rep who gets defensive?

Defensiveness means they heard a verdict. Strip out every interpretation until only camera-observable action remains, then ask before you tell: "what was going through your head there?" If they still push back, don't escalate — turn it into an experiment: "let's both try it on the next call and compare what happens."

Should positive feedback use the same structure?

Yes, and most managers badly underuse it. "Great job" gives the rep nothing repeatable. Name the situation, the specific behavior, and the effect it had — that's what tells them exactly which move to run again, and it makes your critical feedback more credible because you're clearly watching closely either way.

What if a rep keeps agreeing and never changes?

After three cycles of specific, rep-owned feedback on the same behavior with a scheduled re-check each time, stop calling it a feedback problem. It's a will or fit issue, and continuing to coach it just delays a conversation both of you can see coming. Make the next conversation about what's actually going on.

Do I need conversation-intelligence software to do this well?

No — it removes the search cost, not the thinking. The full process runs on recorded Zoom calls, a shared doc per rep, and calendar discipline. It costs the manager more prep minutes per session. Not having a platform is not a valid reason for coaching to not happen.

Sources

• The Feedback Fallacy (Harvard Business Review)
• Use Situation-Behavior-Impact to Understand Intent (Center for Creative Leadership)
• The GROW Model of Coaching and Mentoring (MindTools)
• Sales Coaching (Gong Labs)
• Sales Coaching Techniques (RAIN Group)
• What Good Feedback Really Looks Like (Harvard Business Review)
• Sales Coaching Resources (Sales Hacker)
• Sales Coaching Insights (Korn Ferry)

Related on PULSE

• [How do you coach reps to act on AI call-coaching feedback?](/knowledge/cg0130)
• [How do you give async coaching feedback that lands?](/knowledge/cg0185)
• [How do you deliver tough feedback to a sensitive sales rep?](/knowledge/cg0157)
• [How do you coach reps to commit deals they can actually close?](/knowledge/cg0104)
• [Can you give an example of a reflective question that helps a salesperson realize they are over-engineering solutions?](/knowledge/cg0862)
• [How do you decide whether to push for a close or give the prospect more time?](/knowledge/cg0938)