Change Management for CRM: Why Technology Alone Isn't Enough

Change Management for CRM: Why Technology Alone Isn't Enough

The hardest thing about a CRM project isn't building it. It's getting anyone to use it.

A good user adoption strategy is, together with sponsor engagement and CRM governance, one of the most overlooked success factors in CRM implementation.

That observation sounds obvious enough that it almost doesn't need stating. But every time we walk into an organisation where the CRM investment "didn't deliver what we hoped for", it's the same story: the system was built and delivered on time and on budget. Users got a walkthrough. Then the data went back to Excel, or phone notes, or the head of the one salesperson who "knows everything".

That pattern is not anecdotal. Bain & Company's 2025 Commercial Excellence survey of 1,200+ senior commercial executives across 18 industries found that 70 % of companies struggle to integrate their sales processes into CRM and revenue technologies, and that only about 20 % have realised the full value of their investment. The pattern is global, and it predates the current generation of CRM platforms by a long way. Harvard Business Review covered the same dynamic decades earlier in Why CRM Projects Fail and How to Make Them More Successful.

It's not the technology that fails. It's the change that wasn't led.

Why CRM adoption is harder than for other systems

A new accounting system gets used because it's mandatory. Invoices have to go out, payroll has to run. CRM has no equivalent compulsion. If a salesperson doesn't log a contact, the organisation loses information but the process doesn't stop.

CRM user adoption isn't a technical change. It's voluntary behaviour change, at collective scale. And voluntary behaviour change requires more than a new tool. Whether the platform is Dynamics 365, Salesforce or something else.

Three things make CRM especially difficult:

• It layers on top of an existing, working routine. The salesperson has a way of keeping track of customers that works for them. You're asking them to swap that routine for a new one that hasn't proven itself yet.
• The value is asymmetric in time. The salesperson pays the cost immediately (logging, data entry, learning curve). The value lands with someone else later (sales leader sees pipeline, CFO sees forecast, next salesperson taking over the customer gets history).
• Reverting is free. The Excel sheet is still there. Outlook is still there. If the CRM feels heavy, there's always an exit.

Change management for CRM has to address all three.

Who actually decides the outcome of a CRM change project?

Three roles determine the outcome.

Sponsor. The senior leader who wants the project. If the CEO or sales director regularly asks "what does the CRM say?", behaviour shifts fast. If the sponsor uses Excel themselves, you've lost before you've started.

Champions. Two-to-five people in the organisation who actively want the system. They don't need to be the most senior. Often they're senior salespeople tired of rummaging through email threads, or marketing coordinators who understand that without data, they have no audiences. These people become the front line for adoption.

End users. Everyone else. Adoption is a collective outcome, but it's built one conversation at a time, at the coffee machine, when a colleague asks "how did you do that?".

A CRM project without identified champions loses. Every time.

What needs to be communicated, and by whom?

Many CRM projects start with "we're rolling out [X system]". That's the least interesting message, and the only one that lands in front-of-mind.

Better sequence:

1. Why. What's changing in the business that requires this. Ideally phrased in operational terms: "We're taking on too many customers for Excel to scale", "We're losing information between sales and customer service", "The board wants forecast we can stand behind".
2. What gets better per role. The salesperson gets X. The sales leader gets Y. Customer service gets Z. If you can't phrase it per role, you have a communication job before you have a technical job. (See also Why 70% of CRM initiatives fail for patterns often behind it.)
3. What's expected, concretely. Not "everyone should use the CRM". Rather "all customer dialogues over a certain value are logged within 24 hours". Concrete behavioural expectations are measurable; vague ones aren't.
4. What's not changing. People often fear more change than what's actually happening. Explicitly say "your phone still rings, you still send emails from Outlook, your customer relationships still travel with you".

And: communication has to come from leadership, not from the IT project. Users react to what leadership emphasises. If the sales director doesn't mention CRM in management meetings, neither will sales.

Training that actually sticks

Generic Microsoft videos are wasted time for most organisations. They show how the system works; not how your business uses it.

What works:

• Role-specific training. A salesperson's "day in the system", not a full product demo.
• Classroom + hands-on. One hour of walkthrough followed by two hours of users sitting in their own environment with a trainer present.
• Repetition at day 14, 30 and 60. What people learned in week one, they've forgotten half of by week four. Scheduled repetition, even 30 minutes, solves it.
• Help on demand. An internal Slack channel, a super-user per department, or a short video library covering the three procedures people always forget.

Training without an explicit repetition plan has low adoption impact, regardless of how good round one was.

The first 90 days: where adoption is decided

This is where the CRM implementation is actually decided, not at go-live, but in the first 90 days after. Sales-process adoption depends almost entirely on what happens in this window. We have seen three patterns play out repeatedly across CRM rollouts:

These patterns match what we've seen across years of D365 and Salesforce engagements (From Gut Feeling to Facts covers how adoption connects to value capture).

Pattern A (adoption locks in): After 90 days, the routines are embedded. Salespeople update customers because they feel discomfort when they don't. Sales leader uses the pipeline report in every Tuesday meeting.

Pattern B (adoption stalls): People use the system for what they must, but return to Excel for what they actually trust. Two realities exist in parallel.

Pattern C (adoption collapses): After 30 days, only 2-3 people actively use the system. Everyone else does sporadic compliance.

• Daily visibility of usage. The sales leader sees who is logging interactions and who is not, and asks why.
• Frequent, small adjustments. Fields that do not work get removed. Forms that are too heavy get simplified.
• Visible value. "Last week the report gave me X I would not have seen otherwise", communicated in leadership meetings.

After 90 days the adoption window is largely closed. What has not taken root rarely does later.

Pattern: Across several CRM projects we have seen adoption climb from below 40 % to above 80 % when the organisation pairs the technical implementation with a structured 90-day follow-up plan. The variable is whether someone owns what happens between go-live and steady state.

Concrete example: In one logistics company with 45 sales users, opportunity updates moved from below 30 % consistency to above 85 % after leadership started using CRM pipeline data in weekly operational meetings. The CRM did not change. The expectation around it did.

Measuring CRM adoption: what actually counts

"Number of logins" is not a good metric. People log in to check something, not necessarily to contribute data.

Better adoption metrics:

• Frequency of updates to existing customer records. Not creation of new records, but active maintenance of existing ones.
• Consistency of pipeline-stage updates across sellers. Not "everyone has a number", but "every new opportunity has a realistic close date within 14 days".
• How often leadership uses reports from the CRM in decision meetings. If the answer is "never", the adoption problem is at the top, not the bottom.

Hvorfor endringsledelse for CRM betaler seg

A CRM project where 80 % of users adopt the system within 90 days is an entirely different investment outcome than one where 40 % do. Same licensing. Same implementation. Half the value.

Change management rarely shows up as the most visible line on a project budget, but it is often the line that decides whether the rest of the investment returns anything.

---