Isabelle leads a 35-person department at a 250-employee insurance company. Senior leadership asks her to lead the rollout of a new client file management system, replacing a 12-year-old system employees know by heart, and tells her to "do it quickly."

Isabelle plans the rollout over three weeks: a mandatory two-hour training session, then an email to the whole team announcing that the new system is now the sole standard. She hasn't consulted anyone about the change, hasn't identified any potential obstacles, hasn't named a single champion within the team.

The resistance is immediate. Two senior employees openly state that the old system worked just fine. Several pretend to use the new software while continuing to run the old one in parallel. Six weeks after deployment, 40% of the department is still operating on the old system, doubling their workload. One employee files a union grievance, alleging the change is hurting their productivity.

💬 The Eskalon moment

The question Isabelle could have asked Eskalon before starting: "I have to roll out a new software system and I can already sense resistance before I've even begun. How do I manage the change process to maximize adoption?" The answer rests on a five-step model, applied concretely to her context: help people understand why the change is necessary before any technical training, build the desire to take part by involving the team in the planning, train on the "how," support the practice in the following weeks, and recognize adoption behaviors to make the change stick.

Concretely: hold a team consultation before any formal announcement, identify two or three influential employees ready to become change champions, spread the transition over 60 days instead of forcing an immediate switch, and schedule weekly office hours for employees who are struggling.

With this framework, the same announcement, made within the same tight deadline imposed by leadership, takes on a completely different shape. The team understands the why before the what. Internal champions become natural relays with their peers rather than sources of resistance. The transition unfolds over weeks instead of blowing up over a weekend of rumors. What could have become a project of collective resistance turns into an initiative where the team feels like a stakeholder, rather than a mere recipient of an imposed decision.