There is a moment in sales leadership that catches a lot of people off guard: when you get promoted because you were good at selling. You knew how to build a pipeline, move deals, handle objections, and find a way to hit the number. Then suddenly, your success is no longer measured only by what you can do but by what other people can do because of your leadership.
Early in my leadership career, I thought being a good sales manager meant staying close to the numbers. I inspected the pipeline. I watched activity. I asked about forecasts. I followed up on deals. When performance slipped, I applied more pressure. I was managing, but the problem was that I thought I was developing people. Those are not the same thing.
Management is not bad. Sales teams need it. Someone has to inspect the pipeline, establish expectations, review commitments, and make sure the work gets done. A sales organization without management becomes unpredictable very quickly. But management primarily asks, “Is the work getting done?” Development asks a different question: “Is this person becoming more capable of doing the work well?” That distinction might seem small, but it changes the way you lead.
Imagine a rep has missed target for two consecutive months. The management conversation naturally focuses on pipeline coverage, activity, conversion, and what needs to happen before the end of the month. Those are legitimate questions, but they do not necessarily tell you why the rep is struggling. Maybe the rep does not know how to run discovery effectively. Maybe they understand discovery but cannot translate what they learn into a deal strategy. Maybe they know exactly what to do but simply are not doing enough of it. Those are three very different problems, and treating them as the same problem is where coaching starts to fail.
One of the principles I have come to believe deeply is that leaders need to diagnose before they coach. In Carry the Weight: The Sales Leader’s Guide to Coaching, Trust, and Building People Who Win, I use a framework called EKS: Effort, Knowledge, and Strategy. When performance is not where it needs to be, I want to understand which gap I am actually looking at. Is this an effort problem? Is it a knowledge problem? Or is it a strategy problem? The framework is simple, but it forces a leader to replace assumption with curiosity.
If someone lacks knowledge and I treat it as an effort problem, I may apply pressure to someone who actually needs teaching. If someone has a strategy problem and I send them to another training session, I may give them more information when what they really need is help applying what they already know. If effort is the real issue, another coaching conversation may simply delay the accountability conversation we should already be having.
Development begins when we stop reacting to the visible symptom and start understanding what is underneath it. It also requires us to think beyond the immediate problem. Management often solves what is in front of us. Development helps a person get better at solving the next problem on their own. That matters because the goal of leadership cannot be to make your team permanently dependent on you.
If every difficult deal needs your intervention, you have built dependence. If every objection needs your answer, you have built dependence. If every decision has to come back to you, you have built dependence. It can feel productive because you are busy helping everyone, but being needed for everything is not necessarily evidence of great leadership. Sometimes it shows we have not developed enough capability around us.
This is something I think about often in my broader work as a revenue leader. Real growth is not simply more activity. It is better decisions being made earlier by people you have helped develop. That is how an organization becomes stronger rather than simply busier.
Another practical shift happens when you begin thinking like a developer of people. Sales managers naturally want to know what happened. Why did the deal slip? Why is the pipeline down? Why did conversion drop? Those questions matter, but development requires us to go further. What did you see? What did you miss? What would you do differently? What do you think is getting in your way? What will you try next time?
Those questions require the rep to think, and that matters because coaching should not become a leader handing out conclusions while everyone else takes notes. People need to develop judgment, not just receive instructions. Sometimes the best thing you can do for someone is resist the urge to give them the answer immediately.
The Three Hats framework helps put this into practice: Manager, Coach, Leader. Sales leaders need to know when to manage execution, when to coach capability, and when to lead the person and the broader team. The answer is not to stop managing and become a full-time coach. Sales leaders carry both people and performance. There will be moments when you need to inspect. There will be moments when you need to hold the standard. There will also be moments when you need to stop looking at the spreadsheet long enough to understand the person behind the number. The challenge is knowing which version of you the situation requires.
That is the work. A great sales leader knows when to manage execution and when to develop capability. Because eventually, leadership is not measured only by the number your team produces today. It is also measured by the people they are becoming while producing it.
That is a much heavier responsibility, but it is also the part of leadership that matters long after the quarter closes.
To learn more about Carry the Weight: The Sales Leader’s Guide to Coaching, Trust, and Building People Who Win, visit carrytheweightbook.com.
Also Available On Amazon: https://www.amazon.com/dp/B0HLL9GQL7
