The typical feedback interaction in a sales org goes like this: manager identifies a problem, tells the rep what they did wrong, tells them what to do instead, and moves on. The rep nods, says "great, thanks," and changes nothing. Two weeks later, the manager gives the same feedback on the same issue.
This isn't a rep problem — it's a feedback design problem. Neuroscience research shows that the brain's threat response activates within milliseconds of receiving criticism, literally reducing cognitive function and making it harder to process and retain the feedback. If your delivery triggers defensiveness, the content is irrelevant.
The Situation-Behavior-Impact model provides structure, but adding an inquiry component is what makes it land. Start by describing the specific situation ("In your call with Acme's CFO yesterday"). Then describe the observable behavior ("You spent the first 15 minutes presenting our product before asking any discovery questions"). Then describe the impact ("The CFO disengaged — you could hear it in their responses — and the call ended without a clear next step").
Here's where most managers stop. The critical addition: ask the rep for their perspective. "Walk me through your thinking. What were you trying to accomplish with that approach?" This does two things: it lowers defensiveness because you're showing genuine interest in their reasoning, and it often reveals that the rep has a logic gap (not a skill gap) that's more useful to address.
Feedback delivered 48 hours after the event is 60% less effective than feedback delivered same-day. But immediate feedback in a public setting (like a team pipeline review) can be counterproductive because it triggers social threat responses. The sweet spot: pull the rep aside within 2-4 hours for a brief, private conversation. Keep it focused on one behavior, not a laundry list.
Research on high-performing teams consistently shows a positive-to-constructive feedback ratio between 3:1 and 5:1. This doesn't mean sandwiching criticism between hollow compliments — that pattern is transparent and condescending. It means being genuinely observant about what your reps do well and calling it out with the same specificity and frequency that you use for improvement feedback. When a rep trusts that you see their strengths, they're far more receptive to hearing about their gaps.
Every feedback conversation should end with a specific, observable action the rep will take differently next time. Not "improve your discovery" but "in your next three calls, open with a business context question before any product discussion, and aim for a 40/60 talk-to-listen ratio in the first 15 minutes." Specific, measurable, time-bound.
Then follow up. Check in after the next relevant call. Ask how it went. Acknowledge the effort even if the execution wasn't perfect. This follow-through is what separates feedback that changes behavior from feedback that fills the air and dissipates.