Why your team won't use the CRM (and why more training won't fix it)

In short: CRM adoption usually fails for people reasons, not technical ones. Teams don't use a CRM when they weren't asked what they need, don't understand why it matters to them, and still have somewhere else to go. Fix those first. Accountability comes last. The safety net that sank the system When I joined an £8 million organisation, they had recently moved from Microsoft Dynamics to a new CRM. By the time I arrived, almost nobody was using it properly. The phrase I heard most was some version of: "We don't know why they changed it. Dynamics was so much better." Then I found out why that view never went away. To avoid losing anything in the migration, a couple of Dynamics licences had been kept live. If something was missing from the new system, someone could go back and find it. It was meant as a safety net. In practice, it was the reason the new system never had to work. Every time Dynamics saved the day, it proved the point everyone was already making. The technology wasn't the problem. Nobody had given people a reason to let go. Does this sound familiar? If you're the person who needs your CRM to work, you'll probably recognise some of this. That might be the commercial director, the CIO, or the sponsor whose budget paid for it: • The important information still lives in spreadsheets, inboxes and people's heads. • "It's just more admin" is the standard response. • Each team thinks another team should be keeping it up to date. • Forecasts get pulled together manually because nobody trusts what's in the system. • You've already run training. Maybe twice. None of these is a technology problem. In most cases, the platform does what it was bought to do. The problem is what happened before it went live, and around it since. Why do CRM implementations fail? Most CRM implementations fail because the people expected to use the system weren't part of designing it, and were never given a reason to care about it in their own terms. Every organisation has a department that owns the CRM. Sometimes it's sales, sometimes marketing, operations or IT. That's fine. Ownership naturally brings a bias, because every team understands its own work best. The trouble starts with the step before the build. Did the owning team ask every other department what they need from the system? Did they understand why those teams need it? Usually, not properly. Then comes the language. The owning department tries to win engagement in its own terms. Sales talks about pipeline, conversion and forecast accuracy. To a delivery lead, that means very little. Their question is, "Will this tell me what's coming so I can plan my team?" It's the same data with a different reason to care. If nobody translates it, the message doesn't land. Salespeople need the same translation. They're a key stakeholder in almost every CRM, and many see it as admin at best and Big Brother at worst: something that only comes up when their activity is being reviewed. I know, because I used to feel exactly that. What changed it was a leader who showed me what was in it for me: which clients usually spend more at this time of year, where delivery had flagged an issue I should get ahead of, and which sectors were suddenly worth chasing. That's exactly what had happened in my example. The system leaned towards sales. But its heaviest users were client services, who built solutions and delivery programmes through it, and they had been left out of the conversation. Sales didn't like using it, and the people who relied on it most hadn't been heard. We almost had to start again from scratch. How do you fix poor CRM adoption? You fix poor CRM adoption by going back to the people, not the platform: who touches it, what each of them needs, and why it should matter to them. Here's what that looked like in practice. We built a team with every voice in it. We created an agile working group with one person from every department, including a representative from the executive team. Our project manager led it, with the commercial and operations directors working together as joint sponsors. We mapped the flow before touching the system. We looked at what the organisation needed, what each team needed, and what individuals needed. From that came clear workflows: who does what, why, and who they hand over to. We let teams decide ownership together. Previously, sales were expected to input everything. Once teams were in the same room, client services said they would prefer to hold the admin side of contracts, scheduling meetings and so on. They knew they would do it, and it fed straight into their own work. That one conversation removed a problem that had been blamed on sales for months. We cleaned the data properly. Several hundred hours went into data clean-up. Not glamorous, but nobody trusts a system full of duplicates and dead deals. We trained from the top down. Training started with the executive team and flowed all the way down. Nobody was asked to use something their leaders weren't using. We switched the safety net off. Dynamics was 100% removed. No back door, no fallback. Then, and only then, we enforced accountability. Every spreadsheet used for anything that needed to be reported on or claimed against was taken away. If it wasn't in the CRM, it didn't count. Seven principles for CRM adoption that lasts Strip the story back and the same seven principles apply to any organisation. The order matters. 1. Every touchpoint gets a voice. If a department touches the CRM, it has a say in how it's built. Ask before you build, and understand why each team needs what it needs. 2. Everyone knows the why. Not one reason, three: why it matters to me, to my team, and to the organisation. If people can't answer all three, you haven't finished. 3. Translate, don't broadcast. Speak to each team in its own language. Pipeline means something to sales. Visibility of incoming work means something to delivery. Train in the same way. 4. Show it makes the job easier, not bigger. People use a CRM when it helps them do their job better. If it only feels like more to do, they'll find a way round it. 5. Design ownership together. Let teams agree who inputs what. The people closest to the work often volunteer for more than you'd expect, because they can see the knock-on benefit. 6. Lead from the top and remove the escape routes. Train leaders first and make sure they use it visibly. Switch off the old system and retire the shadow spreadsheets. 7. Accountability comes last. Once people have been heard, know the why and have no back door, enforce it. Enforce it first, and you'll just get better workarounds. What changed when the CRM was finally used properly The biggest change showed up somewhere you might not expect: in client feedback. Because people were following opportunity best practice, the forecast became something everyone could trust and use, not just the commercial team. Client services and delivery could see potential work coming in, well before it was signed. That meant associate delivery could be planned much further in advance. Clients got more stability in who was delivering their work. And that consistency improved the impact they saw inside their own organisations. Client feedback reflected it. The commercial side improved too. With the dirty data stripped out, pipeline reporting became reliable. Alongside a new pricing calculator tool, that clearer view reduced scope creep and improved margins. None of that came from new technology. It came from people understanding why the system mattered, and using it because it helped them. Ten questions to ask about your own CRM If your CRM isn't being used the way you hoped, start here. Any answer that makes you wince points to where adoption is breaking down. • Was every department that touches the CRM involved in designing the processes it supports? • Did the owning team ask what other departments need, and understand why? • Has the purpose been explained in each team's own language, not just the owner's? • Could someone in any team tell you why the CRM matters to them, their team and the organisation? • Can people see how it helps them do their job better, not just give them more to do? • Is it clear who inputs what, and who hands over to whom? • Did training start with leadership, and are leaders visibly using it? • Is the old system fully switched off? • Are spreadsheets still being used for reporting, forecasting or claims? • Is the CRM only ever mentioned when someone's performance is being reviewed? Frequently asked questions What is CRM adoption? CRM adoption is how consistently and accurately people across an organisation use the CRM in their day-to-day work. Good adoption means the data is complete, current and trusted enough to make decisions from. Why is CRM adoption so low? Usually because the people expected to use it weren't involved in designing it, don't understand what's in it for them, and still have an alternative such as an old system or spreadsheets. It's rarely the software itself. Will more CRM training fix poor adoption? Not on its own. Training shows people how to use a system. It doesn't give them a reason to. Without the why, training gets forgotten within weeks. How do you get salespeople to use the CRM? Show them how it helps them sell: spotting buying patterns, seeing delivery issues before the client raises them, and finding similar prospects. If the CRM is only ever used to review their activity, they'll treat it as surveillance. Who should own the CRM? One department can own it, but every department that touches it needs a voice in how it's designed and how it's explained. Ownership without input creates a system that works for one team and frustrates the rest. When should you enforce CRM accountability? Last. Once people have been heard, understand the why and have no fallback system, accountability sticks. Enforced first, it just produces better workarounds. Your CRM probably isn't the problem If your team won't use the CRM, the answer is rarely a new platform or another round of training. It's going back to the conversation that should have happened first: who touches it, what they need, and why it matters to them. I help organisations do exactly that, working with your people, not above them, to design CRM processes every team can see the point of, and the commercial alignment that keeps them used. If this sounds familiar, the first conversation costs nothing. Book a conversation or see how I work. Suzie Thompson is a commercial strategy and sales enablement consultant. She has rebuilt sales and commercial functions from the inside and in supporting roles, with P&L accountability, and coaches commercial leaders at senior and board level.