Change management in IT has become a key issue in large-scale tech projects. Whether it's migrating to the cloud, deploying automation tools, or integrating AI, technological performance alone is no longer enough. Prosci emphasizes that it’s not the technology itself that hinders project success, but the ability of teams to incorporate changes into their day-to-day practices.
In other words, without effective change management, lasting adoption is impossible. By aligning change management with human challenges, we can transform buy-in into a performance driver.
That’s why in this article we explore the practical levers, common pitfalls, and key steps to sustainably increase adoption of your IT projects.
Why change management in IT often fails (and what we can do about it)
Traditional approaches to change management are often linear, rigid and difficult to adjust to the operational reality on the ground. They are often implemented late and limited to top-down communications and generic training, with no real integration into the teams’ day-to-day work.
Excessively rigid traditional approaches
Even the most competent teams can run into difficulties. Too many leaders assume that a simple series of emails is enough to generate user buy-in. As a result, they underestimate the importance of genuine, participatory and engaging mobilization.
Yet without active listening, there can be no lasting buy-in.
For change to be truly integrated, it is essential to:
- Understand users’ concerns
- Consider the reality on the ground
- Use plain and relevant language
By creating spaces for dialogue, valuing everyone’s contributions, and adapting support strategies, technological transformation can become a shared, value-generating force.
As McKinsey summed up in a recent article, “the success of AI projects depends less on the technology than on the ability to align teams and build trust.”
Turning resistance into active engagement
The observation that the success of a project depends primarily on human buy-in applies to all digital transformations. A solution may be perfectly deployed from a technical standpoint, but it can still fail to change practices if users don’t see its value, don’t identify with it, or don’t feel supported.
That said, resistance to change is not a cultural inevitability. It is often the result of a lack of clarity, a sense of insecurity, or insufficient support. When the objectives, reasons for the change, and implementation levers are clearly explained from the outset, stakeholder buy-in becomes significantly easier. This open approach helps shift resistance into active engagement.
The three phases of IT change: before, during and after deployment
Effective change management doesn’t happen by chance, it must be integrated from the earliest stages of the project and continue well beyond its implementation. It’s not limited to a one-off training session or one-way communication but rather forms part of a continuous process involving regular dialogue, active listening, and ongoing adjustments.
According to a recent study by Prosci, projects that incorporate change management from the planning phase are six times more likely to succeed. This data highlights the importance of structured support throughout the transformation cycle. Let’s explore the key levers at each stage of a change management strategy.
1. Before deployment – anticipate and mobilize
- Clarify the project vision: Why this project? Who is it for? What impact will there be on roles, responsibilities, activities, tools, and the company culture?
- Involve key stakeholders from the early stages: to promote buy-in, engagement, and co-construction.
- Map the human and operational impacts: Who will be impacted, how, and when?
- Develop targeted communication strategies and customized training: based on the specific needs of each user group.
2. During deployment – support and adjust
- Mobilize ambassadors: to relay the message, address concerns, and foster close dialogue.
- Offer concrete demonstrations and personalized support: to facilitate appropriation of the changes.
- Adapt communications: based on user profiles, with clear messages disseminated through multiple channels.
- Consistently monitor engagement, understanding, and satisfaction indicators: so you can make real-time adjustments.
3. After deployment – consolidate and evolve
- Collect feedback from the field: through surveys, workshops or direct observation.
- Update training and processes: based on actual expressed needs.
- Maintain targeted support: to strengthen long-term adoption and guard against risks of regression.
Breaking down silos to drive long-term tech adoption
Tech projects go far beyond a single team. They involve several divisions (IT, operations, human resources, finance) and require rigorous cross-functional coordination. Success requires instilling shared responsibility, where each function actively contributes to the transformation.
Change management should not be the sole responsibility of communications or HR. It must be embedded as a collective, integrated skill, activated at every stage of the project. One often underestimated strategic lever is setting up a dedicated change management team to effectively structure the initiative.
Ambassadors play a crucial role in this process. When properly identified, prepared, and supported, they become true catalysts for change. They translate strategic ambitions into tangible benefits for their colleagues while relaying concerns from the field back to decision-makers. This mediating role helps build trust, foster engagement, and embed change over the long term.
The strategic role of IT in change management
Long confined to a technical implementation role, IT teams are actually in a powerful position to support sustainable technology adoption. By engaging as strategic partners alongside other functions, including operations, HR, and finance, they contribute fully to the success of organizational transformation projects.
Their involvement enables them to:
- Anticipate technical or human barriers to adoption, as early as the project’s initial phases.
- Align digital solutions with actual user needs, by putting experience at the centre of decisions.
- Offer targeted support, including practical demonstrations and personalized support to drive ownership.
- Co-create consistent, intuitive, and integrated user paths, in close collaboration with the business teams.
When the IT teams are involved from the planning phase, their role goes well beyond technical execution. They become jointly responsible for the transformation, ensuring successful adoption and tangible improvements in user experience.
Measuring real change: value-oriented indicators
Traditional indicators, such as login counts or number of training sessions completed, only reflect a limited aspect of technology adoption. To meaningfully assess the success of an IT project, it’s essential to move beyond these surface metrics and focus on indicators that reflect real transformation.
- Operational performance: Have processes become more efficient? Are tasks being completed more quickly? Are we seeing a reduction in error rates?
- User experience: Do users feel they are better equipped, more competent, better supported, and more confident using the new tools?
- Integration into practices: Is the tool used regularly, autonomously, and seamlessly within professional routines?
By leveraging these qualitative and operational indicators, assessment shifts from a technical deployment mindset to a value creation mindset. This approach enables measurement of real, lasting adoption and helps tailor support to maximize organizational impact.
Adapting change management to the nature of tech projects
Each technology initiative presents its own challenges, depending on the specific solution being deployed and its organizational impact. A cloud migration, for instance, requires a different approach than integrating artificial intelligence into business processes. The support strategy must be tailored to the unique characteristics of each project.
According to Gartner’s Technology Adoption Roadmap 2025, a project’s effectiveness depends in part on the ability to adapt the change management strategy to the following factors:
- The level of technological complexity introduced
- The degree of automation in the affected processes
- The digital maturity of the organization and its teams
Practical applications of change management in IT
Take the example of Microsoft Copilot: its integration requires careful oversight. Without structured support, the use of generative AI can lead to the indiscriminate reproduction of content. This can weaken critical thinking and compromise the quality of deliverables.
Conversely, a clear strategy positions AI as a tool for intelligent assistance, stimulating reflection and enhancing both individual and collective performance. This framework is essential to ensure that tech adoption becomes a true upskilling opportunity, rather than just functional usage.
How can change management decisively influence the success of a tech project? Here are two real-world examples that illustrate its strategic impact and the levers for generating lasting buy-in.
1. Migration to Windows 11: two models, two outcomes
In one organization, the migration was announced without any formal support plan. The result was widespread disorganization, significant employee disengagement, and an overwhelmed IT helpdesk the day after deployment. Users were poorly informed and unprepared, and productivity dropped sharply.
In contrast, another organization integrated change management from the planning phase. Impacts were anticipated, communications were tailored, and targeted training was delivered. The result was a smooth transition, reassured users, and a significant reduction in support calls.
Three pillars that maximize adoption:
- Prepare
- Inform
- Support
2. AI integration: guided use vs. misuse
In adopting Microsoft Copilot, one organization implemented clear governance and strict usage guidelines. Employees developed a critical and responsible approach, viewing AI as a support tool—not a substitute for professional judgement.
In contrast, the absence of oversight in another organization led to misuse: uncontrolled usage, automated copy-pasting, weakened analysis, and increased risks to deliverable quality. These deviations highlight the importance of ethical, educational, and strategic support when deploying emerging technologies.
Often overlooked aspects of change management
Even the best-designed strategies can fail if certain critical factors are neglected. Three often underestimated elements deserve special attention:
- The role of frontline managers: Too often overshadowed by executives or ambassadors, they are the ones who implement change on the ground and translate strategic direction into concrete actions.
- The domino effect of transformations: Each tech change can trigger others. A simple interface update, for example, might require a complete overhaul of business processes. Anticipating these interconnections helps avoid functional disruptions.
- Organizational fatigue: A rapid succession of changes can lead to fatigue, even when projects are relevant. Identifying this weariness allows for adjustments in pace, tone, and support methods.
Checklist for effective IT change management
For a change management strategy to deliver tangible results, it must be built on structured, rigorous foundations. Too often, key elements are overlooked or minimized, undermining long-term adoption of tech solutions.
To guide actions, secure deployments, and optimize stakeholder engagement, here are the essentials to include:
- Integration from the planning phase
- Mobilization and support of ambassadors
- Personalized training based on user profiles
- Relevant qualitative and quantitative indicators
- Structured follow-up after deployment
- An approach tailored to the type of tech project
Integrating change management into your digital roadmap
Far from being a peripheral or last-minute initiative, change management must be embedded from the design phase. As Atlassian points out, a methodical approach helps to:
- Significantly reduce risks
- Improve the quality of delivered services
- Strengthen organizational resilience in the face of change
Engaging users: the key to a successful tech project
The power of collective intelligence is often underestimated. When users are heard, involved, and valued, they become the primary drivers of change. Even the most resistant individuals can become catalysts for transformation, provided their experience is acknowledged and their voices are heard.
In summary: Technology transforms tools; change management transforms behaviours. The success of a tech project depends as much on the solution as on the buy-in of its users.
A structured change strategy helps to:
- Reduce resistance
- Encourage ownership
- Boost collective performance
- Enrich organizational culture
Preparing for a digital transformation? Our experts can support you in integrating change management into your IT strategy. Contact us to start the conversation.