The most common mistake in team management
After listening to a difficult call, most managers’ default response is to point out what went wrong. “You didn’t ask about the timeline.” “You dropped the price too fast.” “You let the objection go without addressing it.” The rep takes notes. The following week, on the next difficult call, the same patterns come back.
The issue isn’t that feedback is useless. It’s that pointing out mistakes doesn’t build capacity. It builds temporary awareness — and without a system behind it, that awareness disappears under the pressure of the next week of work.
The underlying problem is a widely held misconception: that managing performance and developing a person are the same activity. They’re not. And until they’re separated, the manager works harder and the team improves less than it should.
Feedback and coaching: two different conversations
Feedback is retrospective: it evaluates what happened. Coaching is prospective: it builds the capacity for what comes next. They’re different conversations with different objectives, and mixing them produces one that does neither well.
A manager who only gives feedback tells the rep “that was wrong” — without helping them understand why they did it or how they’ll change in a lasting way. The rep may correct that specific call. But the next novel situation will present the same problem in a different form, because the thinking that drove the behavior was never addressed.
Coaching starts from a different question: not “what did you do wrong?” but “what were you thinking in that moment?” That difference seems small on paper. In practice, it produces completely different conversations.
The question that changes everything
Effective coaching doesn’t start with an evaluation. It starts with genuine curiosity about the rep’s reasoning. Before telling them what they should have done, the manager needs to understand what mental model led the rep to do what they did.
When a manager asks “what were you trying to accomplish when you reached that point in the call?”, something different happens than when they say “you should have done X there.” The rep has to articulate their own thinking — and in doing so, they often identify the problem themselves before the manager points it out.
That’s what builds real autonomy. Not the rep who learned the right answer for that specific situation: the rep who develops the judgment to find the right answer in situations that haven’t happened yet.
It’s also a role shift for the manager. Moving from “the one who knows and corrects” to “the one who asks and listens” isn’t intuitive, especially for managers who got there by being great salespeople themselves. But it’s the shift that separates teams that improve on their own from those that need the manager hovering to function.
The four-step framework
A productive coaching session isn’t a free-form conversation. It has structure. These four steps work as a guide for any call review that aims to produce real development, not just a list of corrections:
Record concrete, observable behavior: “at minute 18, when the prospect mentioned price, you responded with a direct discount.” No interpretation, no verdict. Judgment closes the conversation before it begins.
“What led you to go that route?” before “you should have done X.” The question opens up the rep’s reasoning. The instruction closes it and transfers ownership to the manager.
The goal isn’t to wait to give the answer — it’s to understand the rep’s mental model. Why did they think that was the right path? What information were they missing? What were they prioritizing in that moment? That’s what needs developing, not the surface behavior.
The rep defines the action, not the manager. “What would you try differently next time?” generates more commitment than “next time do this.” The person who designs the plan is the one who feels ownership over executing it.
The sequence matters. Skipping the first two steps to jump straight to “the next step” is the most common trap: you end up with an action plan built without understanding the real problem, and the same pattern keeps showing up in future calls.
From correction to development: how to start this week
The shift doesn’t require more time on the calendar. It requires redirecting the time that already exists toward conversations with a different structure. Three concrete adjustments that can be implemented without reorganizing anything:
- Reserve 15 fixed minutes in each 1:1 for a single call. Not a pipeline summary, not a list of corrections: one call, with the four framework questions. The depth of one well-conducted session is worth more than a superficial review of ten.
- Choose one single behavior to develop per rep, not a list. Lists of five things to improve guarantee that nothing changes. Focus is scarce — assign it accordingly.
- End each session with the rep writing their own next step. Not the manager dictating it: the rep articulating in their own words what they’re going to do differently. That’s commitment, not instruction.
One detail that makes a difference: start the session by asking “what do you think went well on that call?” before going to what went wrong. This isn’t a motivation technique — it’s calibration. Understanding where the rep already has their own judgment helps identify where they still don’t.
What changes in the team
Teams where coaching replaces correction show a pattern that becomes visible relatively quickly: reps start self-correcting before the manager says anything. They come to 1:1s with their own read of the call, identify the moment that didn’t go well, and propose the adjustment. The manager shifts from being the one who detects problems to the one who helps deepen what the rep already identified.
Close rates improve not because every rep learned “the technique,” but because every rep understands their own process well enough to adjust it in real time, without waiting for the Friday review. That’s what differentiates a team that needs constant supervision from one that operates with autonomy.
For the manager, the shift is significant too: less time firefighting deal by deal, more time in conversations that build capacity. Quota pressure doesn’t disappear, but the mechanism for reaching it starts living more inside the team and less on the manager’s shoulders.
Why this doesn’t scale when done manually
Everything above works. It also demands an execution discipline that most managers can’t sustain consistently — not for lack of willingness, but because they have between 8 and 12 reps, pipeline review every week, monthly forecasting, and quota pressure that consumes the calendar before coaching time ever arrives.
The result is predictable: coaching happens when there’s time, which is almost never. And when it does happen, the manager improvises because they don’t have precise information about which behavior is worth working on with each rep this week.
Performy runs this analysis automatically across 100% of calls — not just the ones someone decided to listen to. Every conversation is evaluated against the same behavioral criteria: where the rep explored pain, where they identified the economic buyer, where they conceded before building value. That lets the manager arrive at the 1:1 with the concrete observation already ready and the coaching question prepared — in minutes, not 45 minutes of listening.