Your CRM isn't failing. Your adoption plan is.

There's a conversation that repeats in every company that has bought a serious platform. The licences are paid, the go-live party is over, and a year later a director looks at the usage report and asks: “Why is nobody using it?” Then the familiar answers appear: the tool is clunky, sales people hate admin, we need more training, maybe we bought the wrong system.

I've spent ten years inside these projects — gathering requirements from thousands of users, rolling out Salesforce across five markets, growing BI report usage six-fold on a single programme. Here's the uncomfortable truth: the software is almost never the problem. The absence of an adoption plan is.

The tell-tale symptoms

You can diagnose an adoption failure without opening the system. The signs are organisational:

• The project plan ends at go-live. Everything after — the years when value is supposed to appear — belongs to no one.
• “Adoption” is measured, if at all, as logins. Nobody agreed what good usage looks like for a salesperson, a manager, a marketer.
• Training happened once, as a webinar, before people had a reason to care.
• Leadership sponsors the budget but not the behaviour: managers still accept pipeline updates by email, so the CRM stays empty — and then untrusted, and then abandoned.

What actually works

Make adoption the project. Not a slide in the project — the project. It needs an owner, a budget and a timeline that extends well past go-live.

Agree KPIs with the people being measured. The adoption KPIs that stick are the ones users helped define, because those describe work they recognise as theirs. When I built an adoption strategy for a dealer network across three markets, the KPIs were agreed with the dealers and their managing directors first — and then reviewed weekly at regional governance. Visibility, not pressure, did most of the work.

Win the managers first. One sentence from a sales manager — “if it's not in the CRM, it doesn't exist” — outweighs ten training sessions. Until leaders change what they ask for, users rationally keep their old habits.

Treat enablement as a product. Champions in each team, playbooks for real scenarios, onboarding for every new joiner, office hours when the questions come. A rollout is an event; enablement is a service with a roadmap.

Measure weekly, out loud. Usage data should be looked at as routinely as revenue. Where it dips, that's not an accusation — it's a signal showing exactly where the process and the tool disagree, and where to intervene next.

Buying the platform is a decision. Adoption is a negotiation — with every single user, about whether the new way is worth their effort. You win it person by person, metric by metric.

The payoff

When adoption is run properly, the results stop being abstract: on programmes I've led, BI usage grew 6×, digital lead volume rose 31% for a premium brand, and lead response finally became something you could promise a customer. Same tools. Different plan.

If your usage report is the embarrassing kind, the good news is that this is fixable — usually without buying anything new.