“`html<\/p>\n
Your sales rep just lost another deal because they talked over the customer’s objection instead of listening. You gave them feedback last week about this exact issue, but nothing changed. Sound familiar?<\/p>\n
Most sales managers are giving effective sales feedback constantly. The problem isn’t quantity\u2014it’s that the feedback doesn’t actually land. Your reps nod, say they understand, then walk straight back into the same habits that cost them deals.<\/p>\n
I’ve watched this pattern play out hundreds of times across three CRO roles. The disconnect isn’t about motivation or intelligence. It’s about how we’re wired to receive criticism and how most feedback is structured to be forgotten within hours.<\/p>\n
There’s a canyon-sized gap between hearing feedback and changing behaviour. Your rep can understand every word you say, agree with your assessment, and genuinely want to improve\u2014then revert to their default patterns the moment they’re on their next call.<\/p>\n
This isn’t stubbornness. When we receive negative feedback, our brains trigger the same threat response as physical danger. We’re physiologically incapable of processing constructive feedback when that response is activated.<\/p>\n
Generic praise makes this worse, not better. When you tell a rep they’re “doing great” or “really improving,” they have no idea which specific behaviours to repeat. Same with vague criticism like “you need to be more consultative” or “work on your discovery.” What does that actually mean in the next conversation they have?<\/p>\n
Timing destroys even well-crafted feedback. Wait three days to address an issue, and your rep has already reinforced the wrong behaviour another dozen times. The neural pathways you’re trying to reshape have just gotten deeper. According to Force Management’s research on sales coaching<\/a>, immediate, structured feedback is what separates developmental coaching from ineffective performance reviews.<\/p>\n The real difference between feedback that informs and feedback that transforms is whether it gives someone a clear mental model for what to do differently in the next similar situation. Information without a new action pattern is just noise.<\/p>\n Specificity is non-negotiable. Instead of “you didn’t handle that objection well,” you need “when the prospect said they were concerned about implementation timelines, you immediately jumped to explaining our onboarding process instead of asking what specific timeline pressures they’re facing.” One creates defensiveness and confusion. The other creates a clear before-and-after comparison.<\/p>\n The best feedback I’ve ever given pulled exact phrases from recordings: “You said ‘does that make sense?’ four times in the first ten minutes. Each time, it positioned you as uncertain about whether you were adding value.” That level of detail is impossible to dismiss or misinterpret.<\/p>\n Actionability means every piece of feedback must include a concrete next step. “Listen more” isn’t actionable. “After the prospect shares an objection, pause for two seconds, then ask ‘what’s driving that concern?’ before responding” is actionable. It’s a behaviour they can rehearse and execute in the next conversation.<\/p>\n The distinction matters because vague directives force reps to guess at what you actually want. Concrete behaviours remove all ambiguity. They know exactly what to do differently tomorrow.<\/p>\n Balance matters more than most managers realise. Research shows that 74% of reps say coaching is the number one factor for manager effectiveness\u2014but only when it reinforces what’s working alongside correcting what isn’t. The ratio isn’t about sugar-coating criticism. It’s about building a complete picture of effective versus ineffective patterns.<\/p>\n When you only highlight problems, reps assume everything else they’re doing is wrong too. When you callibrate their strengths against their development areas, they understand which behaviours to amplify and which to eliminate.<\/p>\n Relevance connects feedback to outcomes the rep actually cares about. “This behaviour cost you the deal” is relevant. So is “fixing this will shorten your sales cycle by 15-20%.” Even better: “Senior enterprise buyers interpret this pattern as inexperience, which is why you’re not getting second meetings with VPs.” When reps understand the business physics behind the feedback, they’re far more likely to change.<\/p>\n Worth noting: you must separate behaviour from identity. “You’re not consultative enough” is an identity statement that triggers defensiveness. “In this call, you presented solutions before fully understanding their purchasing process” is a behaviour observation that opens the door to problem-solving.<\/p>\n I’ve used variations of STAR for years because it forces you to be specific and factual before you get to judgement. It also gives reps context they need to understand why a behaviour mattered.<\/p>\n Situation sets the scene: “In yesterday’s discovery call with the VP of Operations at the manufacturing company.” This grounds the feedback in a specific moment, not a general character assessment. It also helps the rep recall the context, which makes the rest of the feedback far more concrete.<\/p>\n The framing prevents you from making sweeping generalisations. “You always interrupt prospects” is unprovable and feels like an attack. “In yesterday’s call, you interrupted three times when the VP was explaining their budget constraints” is observable and discussable.<\/p>\n Task identifies what they were trying to accomplish: “You were working to understand their current process pain points before presenting our solution.” This shows you understand their intent, which reduces defensiveness. It also clarifies the standard they were trying to meet.<\/p>\n Acknowledging intent separates competence from execution. Your rep wasn’t trying to fail\u2014they were attempting the right approach but executing it poorly. That distinction matters psychologically.<\/p>\n Action describes the specific behaviour you observed: “When they mentioned integration challenges with their ERP system, you spent three minutes explaining our technical architecture without asking which ERP they use or what specific integration issues they’ve encountered.” Notice this is pure observation\u2014what you saw and heard\u2014not interpretation.<\/p>\n The more specific you are, the less room there is for misunderstanding. Avoid interpretive language like “you seemed defensive” or “you weren’t listening.” Stick to observable facts: what they said, how long they spoke, which questions they asked or didn’t ask.<\/p>\n Result connects the behaviour to the outcome: “They disengaged, started checking their phone, and cut the call ten minutes early without agreeing to next steps.” This is where reps understand the business consequence. If the behaviour didn’t matter, it wouldn’t be worth addressing.<\/p>\n Consequences make feedback memorable. When reps see the direct line from their actions to lost opportunities, the feedback stops being theoretical and becomes immediately relevant to their commission cheque.<\/p>\n The framework only works if you follow up with collaborative problem-solving. “What do you think you could have done differently?” gets the rep thinking instead of just receiving instructions. Most times, they’ll identify the alternative approach themselves\u2014and when they do, they’re three times more likely to implement it.<\/p>\n Call reviews go sideways when reps feel like you’re looking for mistakes instead of patterns. I start every call review with “what did you think went well?” and “what would you change?” Nine times out of ten, they spot the same issues I would have flagged. When they identify the problem first, the conversation becomes collaborative instead of corrective.<\/p>\n This approach also reveals what they already know versus what they’re genuinely blind to. If a rep can articulate their mistake without prompting, they don’t need coaching on awareness\u2014they need coaching on execution. That’s a completely different conversation.<\/p>\n Single incidents are noise. Patterns are signal. Don’t make a big deal about one awkward transition or one missed follow-up question. Wait until you’ve seen the same behaviour across three or four calls, then say “I’ve noticed a pattern I want to explore with you.” Patterns feel less personal and more fixable than isolated failures.<\/p>\n Pattern recognition also helps reps understand that you’re not nitpicking individual moments. You’re identifying systematic behaviours that, if changed, will improve dozens of future interactions simultaneously.<\/p>\n Side-by-side comparison is brutally effective. Pull two recordings: one where the rep successfully handled a pricing objection, and one where they didn’t. Play them back-to-back and ask “what’s different between these two?” They’ll hear their own contrast in tone, pacing, question quality, and confidence. That’s far more powerful than you explaining the difference.<\/p>\n Self-diagnosis accelerates learning. When reps hear themselves executing both the wrong and right approach, the contrast becomes undeniable. You’re not telling them what’s wrong\u2014you’re showing them their own capability range.<\/p>\n The reps who improve fastest are the ones who build personal improvement playbooks. After each feedback session, they document the specific behaviour to change, the alternative approach to try, and then track when they execute it successfully. This turns abstract coaching into concrete skill-building with visible progress.<\/p>\n Documentation creates accountability without feeling punitive. Reps who write down their development goals are significantly more likely to follow through than those who rely on memory and intention alone.<\/p>\n If you’re only reviewing calls when something went wrong, you’re training your team to hide from feedback. Review winning calls too. Break down what made them work. That creates a culture where call reviews are about learning, not judgement.<\/p>\n Quarterly reviews are useless for behaviour change. By the time you’re reviewing Q2 performance in July, your rep has already reinforced both good and bad habits thousands of times. The feedback-to-application gap is too wide to drive meaningful change.<\/p>\n The problem with infrequent feedback is that it becomes high-stakes. Each quarterly review carries enormous weight, which makes both managers and reps anxious. That anxiety destroys the psychological safety required for honest development conversations.<\/p>\n Weekly micro-coaching works because it catches patterns before they calcify. Fifteen minutes every Monday reviewing two or three calls from the previous week creates a tight feedback loop. Research shows that 71% of teams whose managers coach weekly or monthly follow their sales process consistently, compared to just 29% of teams coached quarterly.<\/p>\n Frequency also normalises feedback. When coaching happens weekly, it stops being an event and becomes a routine. Reps expect it, prepare for it, and treat it as a standard part of their development rather than a performance inquisition.<\/p>\nThe Four Elements of Effective Sales Feedback<\/h2>\n
The STAR Framework for Delivering Effective Sales Feedback<\/h2>\n
Turning Call Reviews Into Behaviour Change Opportunities<\/h2>\n
Building a Continuous Feedback Culture That Scales<\/h2>\n