70% of digital transformation projects fail. In the vast majority of cases, it's not the technology that's to blame. It's people.
This guide shows you how to support your teams so that your digital transformation doesn't become yet another abandoned project after 6 months.
You may have already experienced this situation: a new tool is deployed, management is enthusiastic, but three months later, half the team is still using the old methods. Excel files continue to circulate by email. The CRM is half-filled. The project is officially "ongoing", but unofficially, everyone knows it has failed.
This is not inevitable. Digital change management is a discipline in its own right, and it's based on concrete principles that any SME can apply.
Is your team resistant to change?
Our experts combine technology with human support for transformations that stand the test of time.
Discuss your project →1. Why 70% of digital transformations fail (and it's not the technology)
McKinsey's study is clear: 70% of digital transformation initiatives fail to meet their objectives. The Prosci firm, a specialist in change management, goes further: in 94% of failure cases, the human factor is cited as the primary cause.
The reasons are always the same:
- Resistance to change: Teams don't understand why they need to change their habits
- Lack of training: Tools are deployed without adequate support
- Absence of clear vision: Management knows they need to "go digital" but can't explain the "why"
- No quick wins: Teams see no concrete benefit for months
- Top-down communication: Decisions are made at the top and imposed from above
"Companies don't fail at deploying tools. They fail at changing behaviors."
— John Kotter, professor at Harvard Business School
The good news? These problems are predictable and avoidable. All you need to do is treat digital transformation for what it really is: a human project before it's a technology project.
2. The 5 stages of team adoption
Every team facing major change goes through the same phases. Recognizing them is the first step to supporting them.
Denial
"This won't affect us"
Teams downplay the impact of change. They think it won't concern them, or that the project will be abandoned like previous ones. At this stage, management has announced the project but nobody really believes in it.
How to respond: Communicate the "why" with concrete examples and data. Show the impact on their daily work, not on management's KPIs.
Resistance
"The old system worked great"
This is the most critical phase. Teams actively express their discontent. Arguments fly: "it's too complicated", "we're wasting time", "the old tool was better". Some inadvertently sabotage by continuing to use old methods.
How to respond: Listen. Don't dismiss criticism. Identify legitimate resistance (insufficient training) and emotional resistance (fear of change). Provide immediate support.
Exploration
"Okay, let's try it..."
Teams begin testing the new tools, at first with suspicion. They discover that certain features are indeed useful. This is a fragile phase: a bug or lack of support can swing it back to resistance.
How to respond: Be extremely responsive with support. Every unanswered question is a step backward. Celebrate small victories publicly.
Commitment
"Actually, it's not so bad"
The turning point. Teams see concrete benefits: time savings, fewer errors, better visibility. They even start suggesting improvements. Internal "champions" emerge naturally.
How to respond: Grant autonomy. Let teams customize their usage. Value grassroots initiatives and ideas.
Transformation
"How did we do it before?"
New tools and processes are now part of the team's DNA. Old reflexes have disappeared. Employees themselves become promoters of change with new hires.
How to respond: Document best practices. Capitalize on this momentum to launch the next wave of improvements.
The classic trap: Deploy a tool and expect everyone to jump straight to stage 5. In reality, each person progresses at their own pace, and some can get stuck at stage 2 for weeks if nobody supports them.
3. The fatal mistake: deploy first, train later
This is the "Big Bang" approach: buy the license, configure the tool, send an email to the entire company on a Monday morning: "Hello, from today, we're using [new tool]. Here's the login link. Have a nice day."
This approach fails systematically. Here's why:
Problem 1: Shock of change
Teams find themselves facing a tool they don't know, without a safety net. Productivity drops immediately, reinforcing the feeling that "it was better before".
Problem 2: Lack of context
Nobody has explained WHY this change is necessary. Without the "why", teams perceive the change as arbitrary and pointless.
Problem 3: Late training
Training arrives 2 weeks after deployment. Too late: teams have already developed bad habits or returned to the old system.
Problem 4: Lack of support
Questions accumulate, nobody is available to answer them. Frustration builds, and even the most motivated employees give up.
The approach that works: train BEFORE deploying
Week -4: Communicate about the project, explain the "why", gather expectations
Week -2: Train internal champions on the tool in test environment
Week -1: Practical training for the entire team, with real use cases
Day 0: Supported deployment with immediate support available
Weeks +1 to +4: Enhanced support, Q&A sessions, adjustments
4. The ADKAR model: a proven method for SMEs
The ADKAR model, developed by Prosci, is one of the most widely used change management frameworks in the world. It's particularly well-suited to SMEs because it's simple, actionable, and centered on the individual.
ADKAR is an acronym for the 5 stages each employee must go through:
Awareness
Understanding WHY the change is necessary
Without awareness, there's no motivation to change. Teams must understand the stakes: loss of competitiveness, current inefficiencies, missed opportunities. Be honest about the risks of NOT changing.
Concrete actions: Present figures (time lost, errors, costs). Share examples of competitors who have evolved. Organize collaborative reflection workshops.
Desire
WANTING to participate in the change
Understanding isn't enough; you need to want to. This stage is often overlooked. To create desire, you must answer each employee's question: "What do I get out of it personally?"
Concrete actions: Show individual benefits (fewer tedious tasks, more time for value-added work). Involve teams in tool selection. Identify "early adopters" and give them a leadership role.
Knowledge
Knowing HOW to change
This is training in the broadest sense. Not just "how to use the tool", but "how to integrate the tool into my daily work". Training must be practical, contextual, and progressive.
Concrete actions: Training in small groups (max 8 people). Real use cases, not generic tutorials. Accessible documentation. Regular Q&A sessions.
Ability
BEING ABLE to apply it daily
There's a gap between knowing and being able to. An employee may have completed training but still struggle to apply it in their real context. This is where individual support is essential.
Concrete actions: Individual coaching for complex cases. Transition period where old and new systems coexist. Availability of an internal reference person to answer questions.
Reinforcement
MAINTAINING the change over time
Without reinforcement, old habits return. This stage is the most underestimated. You must create mechanisms that make going back harder than moving forward.
Concrete actions: Disable old tools (no Plan B). Celebrate successes. Integrate new processes into onboarding. Measure and share results regularly.
Practical tip
For each employee or team, identify which ADKAR stage they're at. An employee stuck at "Desire" doesn't need more training (Knowledge), they need to see personal benefits. Adapting your approach to each stage is the key to successful support.
Need a structured framework for your transformation?
We apply the ADKAR model combined with our technology expertise for lasting transformations.
Schedule a discussion →5. Practical tools for change management
The ADKAR model provides the framework. Here are concrete tools to implement it in your SME.
Internal communication plan
Never underestimate communication. A poorly communicated project is a half-failed project. Here's a typical plan:
| Timing | Message | Channel |
|---|---|---|
| D-30 | Project announcement, vision, stakes. "Why we're doing this." | Team meeting |
| D-15 | Tool presentation, demo, Q&A | Interactive workshop |
| D-7 | Champions training, support preparation | Dedicated training |
| Day 0 | Supported launch, support available | Email + Slack/Teams |
| D+7 | Early feedback, adjustments, celebrate quick wins | Team meeting |
| D+30 | Quantified results, share outcomes, plan next steps | Presentation + email |
The quick wins strategy
Nothing convinces better than a fast, visible result. Identify 2-3 "quick wins" that immediately demonstrate the value of change:
Quick Win 1
Automate a tedious task that everyone hates (e.g., manual data entry). Relief is immediate and visible.
Quick Win 2
Create a real-time dashboard that replaces manual weekly reporting. Time savings are quantifiable from the first week.
Quick Win 3
Set up automatic notifications for a process that generated oversights (e.g., customer follow-ups, renewals).
The internal champions network
Champions are your best allies. They're employees who naturally adopt new tools and positively influence their colleagues. We detail this approach in the next section.
6. How to identify and mobilize your internal champions
A "champion" isn't necessarily the most technical person on the team. It's someone who combines three qualities:
- Curiosity: They enjoy discovering new tools and methods
- Influence: Their colleagues listen to them and trust them
- Pragmatism: They understand business challenges, not just technology
Identifying them
In an SME of 20 to 50 people, aim for 2 to 4 champions distributed across different departments. Here's how to spot them:
They're the first to ask questions when the project is announced (curiosity)
Their colleagues naturally come to them when they have a technical problem
They've already taken initiatives to improve their work tools
They have a positive view of change, even if they have reservations
Mobilizing them
An effective champion needs three things:
- Early access: Train them 2 weeks before the rest of the team. They must master the tool and be able to answer basic questions.
- Recognition: Formalize their role. The title "digital contact" or "ambassador" may sound simple, but it gives legitimacy and motivation.
- Dedicated time: A champion who must help colleagues ON TOP of their normal work will quickly burn out. Plan 10-15% of time allocated to support during the transition phase.
"One internal champion convinces more effectively than 10 mandatory training sessions. Peer learning is the most powerful engine of adoption."
7. Measuring adoption: the KPIs that really matter
Many companies measure adoption with just one indicator: the tool login rate. It's insufficient. An employee can log in every day and still not use the tool correctly.
Here are the 4 levels of KPIs to track:
| Level | KPI | Objective |
|---|---|---|
| Usage | Login rate, frequency of use, features used | The tool is used regularly |
| Quality | Data completeness, process compliance, error rate | The tool is used correctly |
| Satisfaction | Internal NPS, satisfaction survey, qualitative feedback | Teams are satisfied with the change |
| Impact | Measured time savings, error reduction, productivity, autonomy | The change delivers business results |
The often-forgotten indicator: autonomy
The true sign of successful adoption is when teams solve their own problems without calling support. Measure the number of internal support tickets: if it decreases week after week, you're on the right track.
The adoption dashboard
Create a simple dashboard (even on Google Sheets) that you share with the entire team each week. Transparency on metrics creates collective momentum. Here's an example:
- Overall usage rate: % of active employees this week
- Completeness score: % of records/data filled correctly
- Time saved this week: estimated based on automations in place
- Pending questions: number of unanswered questions (should trend toward 0)
- Satisfaction score: quick weekly rating (1 to 5)
8. Case study: an SME of 40 people succeeds with transformation
To illustrate these principles, here's the case of an SME in French manufacturing (name anonymized) that we supported.
Context
- Company: Manufacturing SME, 40 employees, Rhone-Alpes region
- Problem: Entirely manual processes (quotes on Excel, customer follow-up by email, no CRM). The manager lost 2 days a week on administrative tasks
- Previous attempt: A CRM deployment had failed 18 months prior, with adoption rate of only 20%
The approach
Audit and listening (2 weeks)
Individual interviews with each department. Identification of real pain points (not management's imagination). Discovery: previous resistance came from lack of training, not rejection of change.
Identification of champions (1 week)
3 champions identified: the sales manager (influential), a technician (curious and organized), the accountant (pragmatic). Each from a different department.
Quick wins first (3 weeks)
Before even mentioning CRM, we automated quote generation (a task everyone hated). Result: 45 minutes saved per quote. The sales team went from skeptical to enthusiastic in a week.
Progressive CRM deployment (6 weeks)
Champions training, then training by department. Each team started with ONE feature, not the entire tool. Daily support for the first 2 weeks.
Automation and reinforcement (4 weeks)
Connected CRM to billing and scheduling. Automatic dashboards. Disabled old Excel files.
Results after 4 months
Adoption rate
92%
vs. 20% on previous attempt
Manager's administrative time
-60%
From 2 days to less than half a day per week
Quote generation time
-70%
From 1h15 to 20 minutes on average
Internal NPS
+47
Team satisfaction score on the project
The key to success? Human support. The tools deployed were nearly the same as 18 months before. The difference: the approach. This time, we put teams at the center of the project, not technology.
9. The JAIKIN approach: technology + human support
At JAIKIN, we've learned something from supporting SMEs: a well-deployed but poorly adopted tool is a wasted investment.
That's why every project we run includes a human dimension as important as the technical dimension:
Audit of usage AND teams
We don't just look at processes. We listen to teams to understand their barriers, habits, and expectations.
Integrated change management plan
Every project includes a communication plan, training strategy, and support timeline. It's not optional, it's systematic.
Contextualized training
No generic tutorials. We train your teams on THEIR use cases, with THEIR data, in THEIR context.
Post-deployment support
We stay available 4 to 8 weeks after deployment. This is the critical phase when teams have the most questions.
Knowledge transfer
Our goal is to make you independent. We train your internal champions so they can maintain and evolve the system without us.
10. Frequently asked questions
How do you support teams in digital transformation of an SME?
Support rests on three pillars: communication (explain the why before the how), contextualized training (on teams' real use cases), and support over time (internal champions, post-deployment availability). The ADKAR model provides a structured framework to guide each employee through change stages.
How long does it take for a team to adopt new digital tools?
On average, expect 2 to 4 months for complete adoption with structured support. Quick wins appear in the first weeks. Without support, the timeline can stretch to 6-12 months, and failure risk increases significantly. The key is to deploy progressively, one feature at a time.
What are the main resistances to digital change in business?
The most common resistances are: fear of job loss (especially with AI), comfort of existing habits, lack of confidence in learning new tools, and feeling that change is imposed without consultation. The solution involves listening, transparency, and team involvement in decisions.
What is the role of an internal champion in change management?
An internal champion is an employee who adopts new tools first and supports colleagues daily. They serve as a bridge between management and teams, report concrete difficulties, and help resolve common problems. In an SME of 20 to 50 people, 2 to 4 well-trained champions are sufficient to drive transformation.
How do you measure the success of digital transformation beyond usage rate?
Usage rate is a necessary but insufficient indicator. Also measure quality (data completeness, process compliance), satisfaction (internal NPS, regular surveys), and business impact (measured time savings, error reduction, productivity). The ultimate indicator is autonomy: when teams solve their own problems without calling support.
Should you train the entire team at once or in groups?
Training in small groups (6 to 8 people maximum) is far more effective. It allows adapting content to each department's context, answering individual questions, and ensuring everyone masters the basics before moving on. Start with internal champions, then deploy department by department.
Sources and references
- McKinsey & Company, "The keys to a successful digital transformation", 2024
- Prosci, "Best Practices in Change Management", 12th Edition, 2025
- Harvard Business Review, "The Hard Side of Change Management" (Sirkin, Keenan, Jackson)
- Kotter, John P., "Leading Change", Harvard Business Review Press
- Bpifrance Le Lab, "Digital transformation of SMEs", 2025
- Gartner, "Top Priorities for IT Leaders in Digital Transformation", 2025
Nous intervenons dans toute la France
Prêt à automatiser vos processus ?
Diagnostic gratuit de 30 minutes. Nous analysons vos workflows actuels et identifions les automatisations les plus impactantes.