BLOG 3: Why CRM Resistance Is Really a Leadership Problem
One idea that really stayed with me from this class is that CRM adoption is usually not a technology problem, it is a people problem. Before reading this case, I honestly thought Salesforce resistance mostly happened because salespeople were lazy, stubborn, or just did not want to learn a new system. But the Marcus Williams case made me see the situation in a more realistic way. His team was not inexperienced or failing. They were actually seasoned B2B salespeople with strong results, high compensation, and years of success without Salesforce. That is exactly why the resistance was so strong. These sales reps did not feel like the system was helping them sell more. Instead, they saw it as more admin work, more monitoring, and more pressure from management. The part that stood out to me most was how Marcus finally realized the issue was tied to time burden, lack of personal value, distrust, fear of transparency, and even concerns about losing ownership of customer relationships. That made the problem feel much deeper than just “please update the CRM.”
What surprised me most is that Marcus had already tried many normal management responses like more training, reminders, recognition, and even warnings, but none of them really solved the issue. That tells me adoption does not happen just because a company buys a system and explains how it works. People need to believe the tool actually supports their own goals. I think that is the biggest lesson for me. In a future sales or management role, I would not assume employees resist change because they are difficult. I would first ask what they believe they are losing. In this case, some reps felt they were losing time, independence, and even job security. That is huge. I also liked the idea that Marcus needed to reframe Salesforce as something that helps salespeople make more money, prioritize better opportunities, and work smarter, not just something that gives management cleaner reports. To me, that is a much stronger leadership approach, because it starts with empathy and then connects change to real value. This case changed how I think about sales technology. A tool can be powerful, but if leadership does not build trust and show personal benefit, even the best system will feel like a burden instead of an advantage.
BLOG 2:Measuring Salespeople Is More Complicated Than I First Thought
Before this week, I used to think evaluating a salesperson was pretty simple. If they sold a lot, they were doing well. If they did not, then they were probably underperforming. But after looking at the difference between behavior, performance, and effectiveness, I realized that sales management is actually way more layered than that. These three ideas sound similar at first, but they are not the same at all, and mixing them up can lead to really unfair judgments.
What really clicked for me is that behavior is about what a salesperson actually does, like calling customers, writing orders, preparing presentations, and putting effort into daily work. Performance is more about whether those behaviors help the organization reach its goals. Then effectiveness is even broader, because it looks at final outcomes like sales volume, market share, or profitability, which can also be influenced by things outside the salesperson’s control, like competitors, company policy, or market conditions. That distinction matters a lot to me, because it shows that a person can work hard, do many of the right behaviors, and still not look “effective” on paper if the outside conditions are bad. I think that is something managers sometimes forget.
The case about Rebecca Thompson made this even more real for me. Rebecca tried to manage everyone using the same system: public rankings, stretch goals, and strong competition. That approach worked for some of her establishment-stage advisors, especially the ones who were ambitious and motivated by recognition. But it hurt others. The exploration-stage advisors felt anxious and discouraged, the maintenance-stage advisors felt disrespected, and the disengagement-stage advisors felt like their different priorities were being ignored. To me, this shows that measuring people only by final outcomes is risky, because it ignores career stage, experience, and what success looks like for different people.
My biggest takeaway is that good sales leadership should not only ask, “Did this person produce results?” It should also ask, “What behaviors are they showing?” and “What factors shaped the result?” I feel like this is a much more human way to manage people. It also connects to fairness, because fair leadership does not always mean treating everyone exactly the same. Sometimes it means understanding where people are in their careers and evaluating them in a way that actually makes sense for their situation. For me, that was the most useful lesson from this week.
BLOG 1: Good Sales Training Is Not Just Teaching Skills, It Is Preparing People for Reality
Before this week, I honestly thought sales training was mostly about teaching people how to sell better, like product knowledge, presentations, and closing techniques. But after looking at the sales training process more carefully, I realized it is much bigger than that. Good training is not just giving information. It starts with figuring out what salespeople actually need, then setting clear and measurable objectives, and then deciding how much the company is willing to invest. That order really matters. If a company skips the needs assessment part, then the training can easily become generic, expensive, and not very useful.
What stood out to me most is that training should be based on real problems, not assumptions. The slides kept showing that managers should look at company goals, observe the sales force, gather customer input, and review records before building a training program. I think that is important because a lot of companies probably jump straight into training without asking what is actually broken. Maybe the issue is not selling technique at all. Maybe the issue is product knowledge, confidence, or even how the company prepares people for changing market conditions. To me, that makes training feel more strategic and less like a random workshop.
I also liked how the material showed there is no single perfect way to train people. Centralized training has benefits because it gives access to stronger instructors, better technology, and direct exposure to top management. But field training also matters because people learn a lot from real customer interactions. At the same time, field training alone can be risky, because new salespeople might copy bad habits from veterans or get an uneven learning experience. So for me, the best approach is probably a combination. I feel like that balance makes the most sense because sales is both structured and unpredictable. You need formal guidance, but you also need real-world practice.
The case and the training ideas together also made me think about how companies support people during difficult times. When markets are bad, companies cannot just expect salespeople to magically perform without giving them better tools, coaching, and realistic support. If someone is working hard but the environment is tough, training can help them adapt instead of just blaming them for low numbers. That feels like a much smarter and more human way to manage performance.
My biggest takeaway from this week is that sales training is not just about teaching someone how to make a sale. It is about helping them succeed in the actual world they are selling in. For me, that is what makes training valuable. It should build skill, confidence, and adaptability, not just check a box.