← All essays

15 March 2026

Your Best Employees Resisting Change? The Psychology Explained

Why do some of the most experienced and capable people in an organisation often resist new systems the most? This essay explores the psychology behind CRM adoption, examining how autonomy, status and competence influence human behaviour during change. Understanding these forces can help organisations move beyond resistance and create lasting, meaningful adoption.


One of the most common misconceptions in business is the belief that resistance to change comes from a lack of intelligence, capability, or professionalism. When a new system is introduced and adoption stalls, the narrative often writes itself. People are resistant. They are unwilling to change. They are stuck in their ways. They do not understand the benefits. If only they embraced the technology, everything would improve. Yet after years of working with Salesforce implementations, I have observed something that appears to contradict this assumption. The people who resist new systems most strongly are often the most capable people in the organisation. Not the new starters. Not the junior employees. Not the people with limited experience. Instead, resistance frequently comes from experienced sales directors, operational leaders, advisors and managers. People who know the business intimately. People who care deeply about performance. People who have spent years building successful ways of working. At first glance, this seems illogical. If a new system improves visibility, collaboration and reporting, surely intelligent professionals should recognise the value immediately. The reality is far more complicated. Because when organisations introduce a platform such as Salesforce, they are not simply introducing software. They are changing the way people experience their work. And whenever that happens, psychology becomes far more important than technology. One of the reasons CRM adoption is so often misunderstood is that organisations tend to approach it as a technical challenge. Processes are designed. Requirements are gathered. Configurations are built. Training materials are created. Go-live plans are executed. Everything is focused on the mechanics of implementation. Yet adoption is rarely determined by mechanics alone. It is determined by human behaviour. Behavioural science tells us that people are motivated by a number of deeply rooted psychological needs. Among the most powerful are autonomy, status and competence. These needs influence how we make decisions, how we respond to change and how we perceive our role within an organisation. When a new system threatens any of these needs, resistance often follows. Not because people dislike technology. Not because they are unwilling to learn. But because they are protecting something they value. The first of these psychological drivers is autonomy. Autonomy is our sense of control over how we perform our work. It is the feeling that we have ownership over our decisions, our methods and our daily activities. For experienced professionals, autonomy is particularly important. Over time, people develop their own ways of working. They build routines, shortcuts and personal systems that help them perform effectively. Salespeople develop methods for managing relationships. Advisors establish ways of organising information. Managers create processes that help them monitor performance. These approaches become part of their professional identity. Then a new CRM system arrives. Suddenly there are mandatory fields to complete, processes to follow and activities that must be logged in a specific way. From a leadership perspective, this creates consistency and visibility. From a user perspective, however, it can feel as though control is being taken away. The challenge is not the technology itself. The challenge is the perception that professional judgement is being replaced by process. This is why the language used during implementations matters so much. Poor training often reinforces the feeling of lost autonomy. Users hear phrases such as, "This is how Salesforce requires it to be done," or, "This is the process you must follow." The focus becomes compliance. Great trainers take a different approach. Rather than focusing on what users must do, they explain why the process exists. They connect activities to outcomes. They show how the system supports the user's work rather than controlling it. That subtle shift transforms the conversation. People are far more willing to adopt structure when they understand its purpose. The second psychological driver is status. Status is one of the most powerful and least discussed forces in organisational change. Every workplace contains individuals who have earned influence through experience, expertise and reputation. They are the people colleagues turn to for answers. They understand customers, processes and organisational history. Their status has been built over years of successful performance. Then a new system arrives and something unusual happens. Everyone becomes a beginner. The expert suddenly has questions. The experienced manager is no longer the most knowledgeable person in the room. The individual who previously solved problems effortlessly now finds themselves navigating unfamiliar screens and workflows. Even when nobody acknowledges it openly, this can feel uncomfortable. Humans are remarkably sensitive to changes in status. We naturally seek situations where we feel competent and respected. When a new system temporarily removes that confidence, resistance can emerge. This helps explain why senior professionals sometimes appear more resistant than newer employees. New employees expect to learn. Experienced employees often expect to already know. When training ignores this reality, it can unintentionally create tension. Experienced professionals may feel they are being treated like novices despite years of expertise. The best trainers understand this dynamic. They recognise that implementation is not about replacing experience. It is about enhancing it. They invite expertise into the conversation. They acknowledge what users already know. They position Salesforce as a tool that supports professional judgement rather than one that replaces it. In doing so, they protect status instead of threatening it. The third psychological driver is competence. Few things are more important to workplace confidence than feeling capable. People want to feel good at their jobs. They want to perform effectively. They want to know that they can complete tasks quickly and accurately. A new system often disrupts that feeling. Activities that were previously straightforward suddenly take longer. Familiar processes feel unfamiliar. Simple tasks become frustrating. Individuals who were once highly efficient may temporarily feel slow and uncertain. This creates an emotional response that organisations often underestimate. People start feeling incompetent. Not permanently, but long enough to become uncomfortable. And when that happens, they naturally gravitate towards whatever makes them feel competent again. They return to spreadsheets. They create side processes. They rely on emails. They use the tools and methods that restore confidence. This behaviour is frequently interpreted as resistance. In reality, it is often an attempt to regain competence. This is why training is so much more than knowledge transfer. Its true purpose is confidence building. The most effective training programmes create opportunities for users to experience success quickly. They use realistic scenarios, hands-on exercises and practical examples. They encourage experimentation in safe environments. They allow people to make mistakes without consequences. Because competence grows through experience. Watching somebody use Salesforce rarely creates confidence. Using Salesforce does. This is why I believe trainers occupy one of the most important yet underestimated positions within any CRM programme. A great trainer sits at the intersection of technology, business process and human psychology. They understand the system, but they also understand people. They know how to explain complexity in simple terms. They know how to remove fear from learning. They know how to translate technical concepts into meaningful business outcomes. Most importantly, they understand that adoption is not achieved through documentation or configuration alone. It is achieved through human interaction. Through conversations. Through coaching. Through practice. Through support. When training is delivered well, something remarkable happens. Users stop seeing the system as something being imposed upon them. They begin seeing it as something that helps them succeed. That shift is often the moment adoption truly begins. For organisations, this understanding creates a significant opportunity. Instead of viewing resistance as a problem to overcome, they can view it as information. Resistance often reveals where autonomy feels threatened, where status feels challenged or where competence feels diminished. Addressing those concerns is frequently more effective than adding more features, more communication or more mandatory training sessions. Because adoption is not fundamentally a technology challenge. It is a human challenge. The next time someone says that users are resisting Salesforce, it may be worth asking a different question. Have we helped them feel capable? Have we respected their experience? Have we shown them how the system supports their work? Because intelligent professionals rarely resist change for the reasons organisations assume. More often, they are responding to the same psychological needs that influence all of us. The organisations that understand this are the ones most likely to achieve lasting adoption. Not because they implemented better technology. But because they created better human experiences around that technology. And in the end, that is what adoption has always been about.