Digital transformation keeps failing at a 70%+ rate. And AI adoption is right on track to do the same. Internal comms can help but the people-side fix is what organizations most often skip.
Here's how internal comms can help this perpetual challenge for organizations.
Remember how Digital Transformation was meant to be more than just applications and tools, it was the promise of a new mindset? A state of mind? A kick-start to the ability to be continuously transforming? But then it kind of ended up being, well, just an awkward tool rollout? And even those didn’t go so great?
The numbers haven't improved much. Research from McKinsey and BCG consistently puts the failure rate for “digital transformation” initiatives at around 70%. Bain's 2024 analysis found that 88% of business transformations fail to achieve their original ambitions. Global digital transformation spending reached $2.5 trillion in 2024 and is projected to hit nearly $4 trillion by 2027. Organizations collectively spend TRILLIONS and still walk away with far less than they set out to accomplish.
Decades of effort. Trillions of dollars. A failure rate that hasn't budged. We can’t roll out tools for finance or intranets or operations without a ton of friction and aggravation, and now AI is somehow supposed to be over, through, and under everything?
What's going on here? How can this get better?
88% of business transformations fail to achieve their original ambitions.
The Problem Is Almost Never the Technology
The root causes of digital transformation failure are pretty well-documented but they don’t get addressed in the same context that decisions actually get made or projects planned.
Research consistently finds that culture, more than technology, is the biggest obstacle to transformation success. Cultural resistance, poor change management (or, more likely: tight budgets in which change management is cut altogether to afford all this fabulous technology), and leadership misalignment rank above technical obstacles as the reasons initiatives stall or collapse entirely.
An example in practice: a team identifies a new tool that promises to improve productivity. IT and procurement evaluate the platform, negotiate contracts, and schedule a rollout. Technical SMEs build training documentation. Then they push it to the organization. Adoption is low. Workarounds proliferate. Six months later, the tool is technically live but practically dormant while employees continue using systems they already understand.
This isn't a hypothetical. It is a pattern that repeats constantly across organizations of every size and sector. BCG's research finds that only 30% of companies navigate digital transformation successfully, leading employees to feel unprepared to handle changes brought by 70% of new technologies, which in turn leads to resistance that undermines all implementations. Even when the technology is ready the organization isn't.
The Cost of Technology Selected Without Context or Input
In many companies, “transformation” is still treated as an IT project, isolated from business strategy and frontline input. The people who work with these tools every day and understand the actual friction points, the workarounds, and the reasons the current system works the way it does are rarely consulted before decisions are made.
Here's a telling sign: consider the example above of a tool that is selected, procured, and rolled-out but not adopted (without consultation for those who will use it). Those are often organizations in which the inverse also plays out: those who do the work identify a tool or a kind of tool they need but can't surmount the internal obstacles to get it selected and procured.
What gets missed is that deploying a new tool is a change to people's working lives.
It asks them to abandon familiar processes, learn new behaviors, and trust that the disruption is worth it. That kind of change doesn't succeed through documentation, a brown-bag, and a go-live date. It requires preparation, communication, and a meaningful answer to the question every employee has when something new lands on their desk: why does this matter to me?
Most organizations have someone whose job is to answer exactly that question but they don't get invited to the planning meeting. Internal communications professionals exist to bridge the gap between organizational decisions and the employee experience of those decisions. Their work is less about announcing things and more about building the conditions under which people can understand, absorb, and act on change.
If you're lucky enough to have dedicated change management help, too, all the better. But it's the context to the greater organizational context that is so often missing and so often the source of why these projects fail. Internal comms is needed at the "design" phase to help connect this to the bigger picture and practical why's and how's that people do their work - not at the end to wrap up the output phase.
Skipping the Very Questions that Would Help Ensure Success
When IT-led transformation initiatives bypass this function, they lose the capacity to translate organizational change into terms that actually move people. What does this tool change about my day? What happens to my current workflow? What does leadership believe this makes possible, and why should I trust that? These are problems that communications can help solve.
Involving communications teams early and not as a final sign-off step, but as co-owners of the change rollout, addresses the adoption gap that technical implementation consistently misses. That means communicators in discovery conversations and in discussions about budget tradeoffs. It calls for involving others, like org design, learning and development, or process optimization into the conversation. It requires understanding the employee's experience of the problem the tool is meant to solve. It makes designing the introduction of change to meet people where they are (not where the implementation timeline assumes they should be) non-negotiable.
This reframe matters for both sides. For IT and operations leaders, it means realizing that communications isn't a downstream task. Rather, it is the infrastructure for adoption. Communications should be in the room before the decision is made, not after the announcement is drafted.
AI Adoption is Repeating the Same Mistakes
If the pattern above sounds familiar, it should. The same dynamics are now playing out in enterprise AI adoption and the stakes are higher.
McKinsey's 2025 workplace research found that employees place high trust in their employers to deploy AI safely and ethically, while simultaneously acknowledging the likelihood that AI may replace a significant portion of their work. That combination of trust and anxiety being felt at the same time describes a workforce that is open to being led well through this transition, and at real risk of being led poorly.
Nearly 7 in 10 workers believe AI will lead to layoffs at their company within the next three years. Almost half fear personally losing their jobs to AI.
The anxiety is real. Gallup's 2025 data shows that 18% of all U.S. employees say it is very or somewhat likely their job will be eliminated within the next five years due to AI or automation and that figure rises to 23% among employees in organizations that have already adopted AI.
Organizations that deploy AI tools without addressing these fears drive them underground, where they express as passive resistance, minimal engagement, and what researchers now call "shadow AI" in which employees use unapproved tools on their own terms because they feel unsupported by official channels.
McKinsey's Superagency in the Workplace Report (January 2025) concludes that the biggest barrier to AI success is not employee resistance but leadership. Employees are ready, or at least ready to learn more. Leadership is failing to create the conditions for adoption to succeed.
The missing conditions are familiar:
- clear communication about what AI is being deployed and why
- honest acknowledgment of what it will and won't change about people's roles
- involvement of employees in identifying the workflow problems these tools are actually meant to solve
Deploying AI as a productivity mandate rather than a workflow improvement misses what actually generates value from these tools. When employees understand the specific problem a tool solves in their work and have some agency in how it gets implemented, adoption follows.
All of this assumes that leaders have a clear understanding of how work flows via workflows in the organization that serves as the “before” in contrast to an AI-optimized “after.” Which if you refer back to the track record of traditional tool rollouts, is a step that many organizations eagerly skip over.
Define What You Are Solving For
The advice to involve employees is often treated as a communications step that happens after a decision is made. But effective AI adoption starts with a diagnostic question before any tool is selected: what specific friction in this person’s work are we trying to remove? Not “how do we get people using AI” but “what is slowing this team down, and is AI actually the right answer?” That question can only be answered by talking to the people doing the work. And the function best positioned to surface those answers at scale, across a workforce, is internal communications. They already know how to ask the right questions and listen to what comes back.
There is also a trust dimension that most AI adoption programs skip entirely. Employees in organizations that have already deployed AI tools are more likely to fear job displacement, not less, which means successful deployment of one tool can make the next rollout harder if the communication around the first one was evasive or incomplete. The fear does not dissipate because a tool works. It compounds if leadership never directly addressed it.
Organizations that are honest about what AI will and will not change about people’s roles and that make that honesty a consistent pattern, not a one-time announcement, are building the trust conditions that make future adoption easier. That is a communications architecture that solves fundamental problems for these kinds of projects, and it requires communications professionals in the room when the adoption strategy is designed.
In practice, this means two conversations that most rollouts skip.
- Before decisions are approved and before deployment: sit down with employees and ask what problem they want solved.
- Before launch communications go out: sit down with your communications team and agree on what you are committing to say, consistently, when people ask what this means for their job.
Neither conversation takes long. Both determine whether what follows is adoption or avoidance.
What Getting it Right Looks Like
The organizations that navigate digital transformation and AI adoption more successfully tend to share a few characteristics.
They involve employees in defining the problems before selecting the solutions. They communicate the why behind new tools as a genuine attempt to make change legible to the people it affects, not just a messaging exercise. And they recognize that communications professionals are not the people who announce the new platform after the decision is made; they are the people who help the organization understand what it's asking of employees, and how to ask it well.
The technology questions in digital transformation are largely solved. Platforms work. AI tools are evolving. The question of whether an organization can get its people to adopt them, use them well, and trust that the investment serves them as much as it serves the bottom line? That question remains stubbornly open.
Answering it starts with treating the employee experience of change as a first-order concern, not a communications cleanup task at the end.
FAQs
Why do most digital transformation projects fail?
Research from McKinsey, BCG, and Bain consistently shows failure rates between 70–88%. The primary causes are not technical: they are cultural resistance, poor change management, and leadership misalignment. Organizations that treat digital transformation as an IT project rather than an organizational change initiative consistently underperform.
What role does internal communications play in digital transformation?
Internal communications teams help translate organizational change into the terms employees need to act on it. Any true transformation is a business transformation, and you need the larger context of the organization in the picture to achieve that. When comms is involved early before a tool is chosen and before it is deployed, not after, they can address the practical and emotional dimensions of adoption: what does this mean, what changes, what doesn't, and why it matters. Their involvement is a driver of adoption.
Is AI adoption different from other digital transformation initiatives?
The change management challenges are the same, but the anxiety is higher. The tools are evolving quickly and the hype is deafening. The fear of missing out or being left behind is powerful. Employees have real concerns about job displacement; Gallup's 2025 data shows nearly 1 in 5 U.S. workers believe AI will eliminate their job within five years. Organizations that address those concerns directly, involve employees in identifying AI use cases, and communicate honestly about what will and won't change see meaningfully better adoption outcomes.
How can IT and communications teams work together more effectively?
The most effective shift is structural: bringing communications into initiative planning rather than deployment announcement. That means communicators in early discovery conversations, contributing to how the problem is framed and how employee impact is understood, not just writing the launch email.
Want to explore how internal comms can support your next transformation intiative?
There is likely someone in your organization who wants to cut the budget or accelerate the timeline - and skip the very steps that will ensure success for whatever business transformation you have coming on the horizon. Let's discuss.