Zhenxiang's MGMT 153 BLOG

Why CRM Resistance Is Really a Leadership Problem

One thing that really stood out to me from this class was that CRM failure is usually not a technology problem. At first, I think a lot of people, including me, might assume that if a sales team is not using Salesforce, the system is probably too hard, too confusing, or just badly designed. But after reading the Marcus Williams case, I started to see that the deeper issue is not the software itself. The real problem is resistance, trust, and change management. Marcus’s team only had a 34 percent adoption rate even after eighteen months, and that is kind of shocking when you remember this was an experienced B2B sales team selling complex industrial solutions with long sales cycles, multiple stakeholders, and deals that could reach into the millions. In a sales environment like that, a CRM should be extremely valuable, yet the team still resisted it. That made me realize that people do not automatically adopt a system just because management says it is useful.

What surprised me most was how reasonable some of the resistance actually sounded. The salespeople were not just being lazy. They felt Salesforce created extra administrative work, did not help them personally, and gave management more power to monitor them. Some even worried that putting all of their relationship knowledge into a shared system would make them easier to replace. Honestly, I can understand why that would feel threatening, especially for veteran reps who built their success on personal relationships and independence. I think this is what makes the case so interesting. Marcus cannot solve this by just forcing compliance harder. If he wants real adoption, he has to change the team’s mindset and show that Salesforce is not only for leadership reporting, but also for helping reps prioritize deals, manage complex stakeholders, and avoid losing important information across long sales cycles. That is a much more human challenge than a technical one.

For me, the biggest takeaway is that sales leaders need to sell change the same way they sell products. They need to understand objections, show real value, reduce friction, and build trust before expecting commitment. I think this matters a lot because in my future career, I probably will work with teams, systems, and process changes that look good on paper but fail in practice if people do not buy in. This case reminded me that even the best tool can fail when leadership ignores the emotional side of adoption. That was probably the most useful insight for me from this class.

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.

WEEK 9

留下评论