Digital transformationCRM adoption

Why CRM projects fail: 7 strategies to encourage user adoption

Why CRM adoption fails, what the studies say, and 7 sourced strategies (ADKAR, Kotter, Microsoft, Salesforce) with a 10-step plan.

Mehdi B.

Co-founder · SEO & digital strategy

Why CRM projects fail: 7 strategies to encourage user adoption
In brief

A CRM rarely fails because of the software alone: it fails when teams see no benefit for themselves and go back to their spreadsheets. At Smart Impact, CRM adoption is prepared like an organisational project: start from real work, a manager who uses the tool, a scaled-down first version, training by role, internal champions and usage tracking.

A CRM project rarely fails on the day the software is installed. It fails a few months later, when the sales team goes back to its Excel file and management discovers that the client records no longer reflect reality. CRM adoption, meaning regular use of the tool by the people who have to feed it, is therefore prepared well before go-live. At Smart Impact, we see the CRM as an organisational project before an IT project: the choice of software matters, but it almost never decides the outcome on its own.

Each of the seven strategies below draws on a published, verifiable framework: Prosci's ADKAR model, John Kotter's eight steps, Microsoft and Salesforce documentation, and Nielsen Norman Group's work on user testing. None is enough on its own. Together, they address the causes of abandonment that studies describe, and they end with a ten-step action plan designed for an SME in French-speaking Switzerland.

Why CRM adoption fails: what the studies really say

Let us start with the figures, because they circulate widely and are hard to verify. The CRM failure rates repeated from article to article vary greatly from one source to another, and they rarely come with a date or a method. The firm Johnny Grow, which publishes a report on the subject, points out that everything depends on the definition used: for them, a failure is a deployment that did not meet its intended objectives. A project delivered late but used therefore does not fall into the same category as an abandoned CRM.

The dated studies we were able to read tell a more nuanced story. In 2002, AMR Research surveyed 80 reference accounts of the twelve main CRM vendors, according to destinationCRM's report: 47% of these companies reported serious difficulties with end-user adoption, often to the point of endangering the project. In March 2009, William Band, an analyst at Forrester, detailed in CRM Magazine a survey in which more than 200 problems had been reported. Technology accounted for 33%, business processes 27%, people issues 22% and strategy 18%. Among the people issues, 49% concerned the difficulty of achieving adoption, 36% insufficient preparation of change management and 15% cultural resistance.

These two studies therefore do not say quite the same thing. AMR places adoption at the heart of the difficulties, whereas Forrester ranks technology first and people issues third. They do not measure the same thing: the first counts companies in difficulty, the second breaks down reported problems. Our reading is cautious. Adoption does not explain failures on its own, but it comes up in every survey, and it is the part of the project that an SME controls best.

Prosci offers a complementary view, broader than CRM. In an article published in 2023 based on responses from more than 2,600 change practitioners, the firm reports that 88% of projects with change management rated excellent met or exceeded their objectives, compared with 13% when it was rated poor. This is a self-assessment by respondents and covers projects of all kinds. The figure indicates a trend, not a forecast for your own deployment.

Strategy 1: start from the teams' real work before configuring

A CRM is adopted when it solves problems users already experience: a client history that cannot be found, a forgotten follow-up, information stuck in the mailbox of an absent colleague. Microsoft's checklist for Dynamics 365 projects starts there, in fact. It is about defining what changes, then determining which users or groups of users are affected, before any question of configuration.

In practice, this means a few half-days of observation and interviews. You watch how a salesperson prepares a meeting, how the assistant finds a proposal, how support hands over a case. The workarounds the teams have invented, such as a shared spreadsheet or a notebook, are valuable: they show what the teams really need.

Take an accounting firm of fifteen people in Fribourg. Engagements are tracked in a spreadsheet, tax deadlines in personal diaries, and client exchanges stay in everyone's own mailbox. Before comparing software, the team does well to list the three or four situations where information gets lost. The CRM is then configured for those situations, and not for the full range of its features.

It remains to check that the configuration holds up. Since a March 2000 article, Jakob Nielsen of Nielsen Norman Group has defended an idea that applies well to CRM: rather than one large, costly test, three small rounds of tests with five users each are better, fixing issues between rounds. In the same spirit, Microsoft recommends testing the solution with familiar data and scenarios drawn from an ordinary working day.

Strategy 2: give everyone a personal reason to change

The ADKAR model, developed by Jeff Hiatt, founder of Prosci, describes change at the level of the individual. It chains five elements: awareness of the reason for change, desire to take part, knowledge of how to do it, ability to do it day to day, and reinforcement that prevents a return to old habits. Prosci sums it up this way: organisational change happens one person at a time.

A common mistake is to start with training, that is with knowledge, when the first two stages have not been passed. An employee who does not see why they should enter their meetings will retain little of what they are shown. Microsoft says it in its own way in its training guide for Dynamics 365: employees must understand the why of the materials and scenarios presented to them, and training must stay useful without overwhelming them.

The why must therefore be put into words role by role. For a heating and plumbing company in Sion, the argument for technicians is not management's visibility of the pipeline. It is finding the installation history on their phone before arriving at the client's, and no longer calling the office for a serial number. If the only announced benefit is control, the tool will be seen as a surveillance instrument, and resistance will be logical. We detail this mechanism in our article on employee resistance to new digital tools.

John Kotter, who observed more than a hundred companies in transformation for his March-April 1995 Harvard Business Review article, also puts the reason to act first: the first of his eight steps is to create a sense of urgency. For a CRM, this urgency is told with facts the team recognises: the client lost because a follow-up fell between two people, the proposal redone twice.

Strategy 3: a manager who uses the CRM themselves

Prosci sums up the sponsor's role in three requirements. The sponsor takes part actively and visibly throughout the project, and not only in the kick-off meeting. They rally the other leaders around the change. They explain the reasons for the change to those concerned themselves. In its studies, the firm observes that projects with a highly effective sponsor meet their objectives significantly more often than those whose sponsor is ineffective.

In an SME, the sponsor is generally the managing director. Salesforce's Trailhead module on adoption stresses a very concrete point: leaders must use the tool and expect everyone else to do the same. The example given is a vice president who asked his directors for live pipeline reports in Salesforce rather than in spreadsheets, which made the CRM the reference tool.

The practical translation comes down to one simple rule. The weekly sales review is held on screen, in the CRM, and a deal that is not in it is not discussed. The day the manager accepts a table sent separately, the team understands that the CRM is optional. Our leader's guide to introducing a new technology develops this stance beyond the CRM alone.

Strategy 4: launch a scaled-down first version

A CRM on the market offers far more features than an SME will use in its first year. Switching everything on at once multiplies fields, menus and opportunities for error. Gartner has measured this overload among sellers: according to the report published by destinationCRM in October 2024, half of the sellers surveyed say they are overwhelmed by the amount of technology needed for their work, and they are 45% less likely to reach their sales target.

Microsoft's documentation describes the alternative to the single deployment known as “big bang”: a phased deployment, where features go live over time. Each phase then has its own, more condensed training plan, which builds on what was learned in the previous one.

For the first version, we recommend starting from the situations identified in strategy 1 and sticking to them. That means few mandatory fields on a contact record, different views for sales and for management, and the company's own vocabulary rather than the vendor's. If your teams talk about “engagements” and not “opportunities”, the CRM should talk about engagements. Advanced dashboards, forecasting and automations will come in a second phase, once basic usage is established.

A person interacts with a virtual customer relationship management interface displaying “customer relationship management” icons, sitting at a desk with an open laptop.

Strategy 5: train by role, at the right time, and after launch

The Dynamics 365 implementation guide makes training a continuous process. It asks for the training plan, with the people and resources needed, to be drawn up at the start of the project, and for the content to be ready well before the sessions. It also recommends training objectives that are measurable and tied to adoption, not only to attendance rate.

The same guide points out a frequent blind spot: people who arrive after launch. They often receive fewer resources than those present at the start, even though they have to learn their job and the tool at the same time. In an SME where every hire counts, onboarding a new employee should include a CRM walkthrough, based on existing materials.

Finally, Microsoft advises identifying, during and after the sessions, the tasks on which users get stuck, in order to produce targeted content afterwards. Salesforce recommends placing help where people work, for example in a company-specific help menu built into the tool. A short sheet per role, accessible from the CRM, is often more useful than a long manual.

Strategy 6: rely on internal champions

The sponsor cannot support every user. Kotter makes building a coalition, then an “army of volunteers”, two full steps of his method, followed by removing the obstacles that prevent action. Prosci asks the sponsor to rally other leaders. For its part, Microsoft's checklist provides for clearly designating who carries the change management activities and drawing up an individual support plan.

In a team of twenty or thirty people, one or two champions per department is often enough. They are respected colleagues, trained a little earlier and a little more thoroughly, to whom everyday questions are put without going through management. Their role is also to report what is getting stuck. A field considered useless by the entire sales department must be able to disappear quickly, otherwise the champions lose credibility.

Take an engineering firm in Neuchâtel rolling out a CRM to track its proposals. A project manager already comfortable with the tool becomes the go-to person for her team. She spends part of her week on her colleagues' questions during the first months, with management's explicit agreement. Without this recognised time, the champion role remains a good intention.

Strategy 7: measure usage and reinforce good habits

The last letter of ADKAR, reinforcement, is the one that projects readily neglect once launch is over. It serves to sustain the new way of working and to avoid a return to old habits. Kotter says the same with his last steps: generate short-term wins, sustain momentum, then anchor the change in the company's culture.

Salesforce offers a simple tool: a dashboard showing frequency of use per person, with indicators such as login days or opportunities created, and a version for each team lead. Microsoft's checklist includes measuring adoption and usage, putting recognition and corrective actions in place, and removing technical, human and organisational obstacles.

Two caveats, however. A login does not prove useful use. It is better to also track data quality: up-to-date records, deals with a dated next step, fewer duplicates. The Trailhead module also suggests publicly displaying the ranking of users. In a small team in French-speaking Switzerland where everyone knows each other, we generally prefer a one-to-one conversation and highlighting concrete successes, such as a deal signed thanks to a follow-up scheduled in the CRM.

Four colleagues using digital devices in front of a wall illustrating teamwork.

10-step action plan for CRM adoption in an SME in French-speaking Switzerland

This plan covers the seven strategies in chronological order. Durations depend on the size of the team and the number of tools to connect, which is why we do not set them here.

  1. Name the sponsor and the change lead. The manager commits to steering sales activity in the CRM. An identified person carries communication, training and follow-up, with time set aside for it (strategies 3 and 6).
  2. Write down what changes and for whom. For each role, one sentence describes what will be different in their week, following the approach of Microsoft's checklist (strategy 1).
  3. Observe the real work. A few interviews and observation sessions make it possible to identify the situations where information gets lost and the existing workarounds (strategy 1).
  4. Set three or four usage indicators before configuring. For example, the share of ongoing deals entered in the CRM or the share of records with a dated next action. These indicators are then used for follow-up (strategy 7).
  5. Configure a scaled-down first version. Only the features that address the situations identified in step 3 are activated, with the company's vocabulary and views by role (strategy 4).
  6. Test in small rounds. Three rounds with five users, on familiar data and scenarios from an ordinary day, with corrections between each round (strategy 1).
  7. Explain the why, role by role. The sponsor presents the reasons for the project themselves, then each manager translates the benefit for their team, before any training (strategy 2).
  8. Train the champions, then the teams, just before launch. The champions are trained first. The following sessions are organised by role and cover the few essential tasks, with help accessible from the tool (strategies 5 and 6).
  9. Launch with reinforced support. During the first weeks, the champions are available, blockers are noted and fixed quickly, and the sales review is held in the CRM from the first week (strategies 3 and 6).
  10. Measure, reinforce and prepare the next phase. The step 4 indicators are reviewed every month, early successes are shared, new employees receive a CRM walkthrough, and advanced features are added in phases (strategies 4, 5 and 7).

Typical scenario: an SME of twenty-five people in Lausanne

Imagine an IT services company of twenty-five people in Lausanne. It bought a CRM two years ago. The sales team uses it for new prospects, but existing clients are tracked in a spreadsheet and the technicians have never had access to it. Management is considering changing software.

Going through the plan, the team first finds that the software is not the main problem. No one explained to the technicians what the CRM would bring them, the sales review is still held on the spreadsheet, and the contact record has about twenty fields, many of them mandatory. The first decision is therefore to shrink the record, open a simple view for the technicians, hold the review in the tool and appoint a champion in each team. Changing software is only reconsidered after a few months of tracking usage indicators. This scenario is not a client case: it illustrates the order of the questions we ask.

If your CRM remains underused, or if you are preparing a rollout, let us talk about it in a first conversation: we will look with you at where the blockage lies before talking about tools.

Sources

crm adoptionchange managementcrm project failuremanaging changecrm implementationadkar modelproscikotterdigital transformation
Mehdi B.
About the authorMehdi B.

Co-founder of Smart Impact. Hooked on the web from the start, he launched his first project in 2006: an online music magazine still running today. With close to 20 years of SEO experience, a Swiss federal diploma in marketing and a solid geek streak, he turns clients' ideas, sometimes hazy ones, into concrete digital projects with his team.

LinkedIn
Further reading