AI transformation isn't a tech project. Stop treating it like one.
by Bill Briggs, Chief Technology Officer, Deloitte Consulting
Editor’s note: To our subscribers who have been following the publication for any length of time, you may notice some changes to the look and feel of our site and newsletter. It’s part of an effort to refresh the publication and make it more relevant to practitioners building the enterprises of tomorrow. What isn’t changing is our commitment to bringing you the perspectives you need to make sense of the latest technology trends. And so without further ado, here’s today’s post from Deloitte’s chief technology officer, Bill Briggs
AI transformation isn’t a tech project. Stop treating it like one.
Too many enterprises treat AI like any other technology implementation. What they’re missing is the crucial role process redesign and change management play.
When I look at the AI programs running inside most large enterprises right now, I see a familiar pattern. Substantial investment has gone in. Pilots have been stood up. A center of excellence exists somewhere on the org chart. And yet, when you ask leaders to point to something that has fundamentally changed about how their business operates, the answers tend to get vague.
There’s a reason for that. We’ve been treating AI transformation as a technology project, and technology projects don’t transform organizations. People do. Process does. Leadership alignment does.
The investment imbalance
Here’s a data point that surprised me: our research shows that organizations are putting 93% of their AI investment into technology — the models, the chips, the deployment infrastructure — and only 7% into the people, workflows, and cultural change required to actually use it.1 When I came across that figure, my first reaction was disbelief. My second was recognition. I had felt that imbalance in conversations with clients across industries for months, but I hadn’t been able to quantify it until now.
What passes for “transformation” in a lot of organizations right now is really just procurement. And when the technology doesn’t deliver value, leaders often conclude that the technology failed them. In most cases, the technology wasn’t the problem.
Weaponizing inefficiency
There’s a pattern I’ve seen repeat itself across every major technology wave of the past 30 years, and AI is no exception. The path of least resistance is always to take the new technology and apply it to the way you’ve always worked. It’s fast, it’s familiar, and it avoids the hard conversations about process redesign and organizational change.
The problem is that it doesn’t work. Worse than that, with AI, it can actively make things worse.
If you take an inefficient workflow and automate it with agents, you haven’t eliminated the inefficiency. You’ve accelerated it. You’ve turned what was once a slow, human-paced problem into a fast, machine-paced one, and now you’re paying for it per clock cycle.2 I call this “weaponizing inefficiency.” You meant to build a competitive advantage and instead you built a cost machine.
We saw something similar during the cloud migration era. Organizations moved their legacy processes to the cloud and declared themselves transformed. Then the bills arrived. What looked like modernization was actually just a more expensive version of the old way of working. The same dynamic is unfolding right now with agentic AI, and the stakes are even higher because agents operate with a degree of autonomy that makes course corrections harder.
Grace Hopper, one of the founding figures of modern computing, had a phrase for this kind of thinking: “The most dangerous phrase in the language is ‘we’ve always done it this way.’”34That phrase has derailed more transformations than any technical failure I’ve ever seen.
The trust gap hiding in plain sight
Beyond the investment imbalance, there’s a structural problem with how most organizations have approached AI rollout, and it shows up in the data on workforce trust.
We conducted a study on AI trust levels across organizational hierarchies and found that managers and leadership report 26% and 40% higher trust respectively than the average across employee levels, while Staff score 53% below that average.
That gap isn’t a communications problem. It’s a design problem. Organizations built their AI strategies in the executive suite, announced them from the top down, and expected adoption to follow. But frontline employees — the people closest to the actual work — were never part of the conversation about how AI would be used, what it would change, or what it would mean for their roles. So they didn’t trust it. And in many cases, they quietly worked around it.
The irony is that those frontline employees are exactly the people best positioned to identify where AI can actually create value. They know where the friction is. They know which tasks are genuinely tedious and which ones require judgment that can’t yet be automated. When you leave them out of the design process, you don’t just lose their trust. You lose their knowledge.
There’s also a shadow AI problem emerging as a direct consequence of this trust gap. According to Deloitte research, 43% of workers with access to approved AI tools admit to using unauthorized alternatives instead — tools they describe as easier to use and more accurate than what their employers provided.5 That’s not a cybersecurity footnote. That’s a signal that the official AI program isn’t meeting workers where they are.
HR for machines
One area where I think the framing needs to shift dramatically is how we govern AI agents. Right now, most governance conversations are about guardrails — what can the tool do, what is it prohibited from doing, how do we audit outputs. Those are important questions, but they miss something bigger.
As organizations move from deploying a handful of AI tools to running hundreds or thousands of agents across their operations, the governance question starts to look a lot less like a compliance problem and a lot more like a workforce management problem.
Some of the most sophisticated organizations we work with are beginning to treat AI agents almost like employees. They have onboarding processes that define what data the agent can access, what decisions it’s authorized to make, and what actions require escalation. They have performance management policies that evaluate whether the agent is behaving as expected, how its patterns have drifted, and whether it need to be retrained or retired. And they have offboarding policies that determine who inherits accountability for an agent’s decisions once it’s decommissioned.
I’ve raised what might seem like an absurd hypothetical, but it points to a real problem: imagine a human employee creates an agent, that agent spins up five more agents, and a decision made by a fifth-generation agent causes harm. Who’s accountable? What’s the appropriate response?6 These are governance questions, and right now most organizations don’t have answers.
The companies getting ahead of this are the ones treating their AI agents like a silicon-based workforce — thinking seriously about what an HR operating model looks like for digital workers, not just for human ones.
What it actually takes
I’ve said this in boardrooms and I’ll say it here: the technology is ready. Right now, today, without a single additional line of code being written, there is enough proven capability in existing models and agentic frameworks to fundamentally transform how most organizations operate.7 The limiting factor is not the technology. It’s whether leadership is willing to do the harder work.
That work has a few components.
It starts with the CEO making clear, publicly and consistently, that the organization is going to reimagine how it works, not layer AI on top of old workflows, but genuinely rethink them. Enterprises need to have the CEO saying that the organization is going to reimagine everything. This is a moment in time for us to really rewire the nervous system of the entire organization.8
It also requires the executive team to operate in genuine alignment — not just alignment on the aspiration, but on the specific tradeoffs. What does the organization stop doing? How does it handle the workflow disruption that real redesign creates? How does it invest in helping workers whose roles are most affected? According to Deloitte’s Tech Trends 2026 report, virtually every organization we studied is undergoing some form of operating model change as a result of AI — only 1% reported no changes at all.9 The question is whether those changes are being driven by strategy or by accident.
And it requires patience with the learning curve. The organizations I’ve seen succeed with AI aren’t the ones who moved fastest to deploy. They’re the ones who built genuine feedback loops, structured ways that allow them to understand what’s working, what isn’t, and how to improve. That sounds obvious. It’s remarkably uncommon.
The message to anyone waiting for the right moment: paralysis is not a strategy. No matter how much traffic there is, the sooner you leave, the sooner you can get there.”10
Join our community to get emerging tech insights every week.
Have you seen similar trends in your industry? Share your thoughts in the comments below.
If this post resonated, forward it to colleagues who would also find the insights helpful!
-- Bill Briggs | Chief Technology Officer | Deloitte Consulting.
This article contains general information only and Deloitte is not, by means of this article, rendering accounting, business, financial, investment, legal, tax, or other professional advice or se2rvices. This article is not a substitute for such professional advice or services, nor should it be used as a basis for any decision or action that may affect your business. Before making any decision or taking any action that may affect your business, you should consult a qualified professional advisor. Deloitte shall not be responsible for any loss sustained by any person who relies on this article.
As used in this document, “Deloitte” means Deloitte Consulting LLP, a subsidiary of Deloitte LLP. Please see www.deloitte.com/us/about for a detailed description of our legal structure. Certain services may not be available to attest clients under the rules and regulations of public accounting.
Copyright © 2026 Deloitte Development LLC. All rights reserved.
Hulme, Digital CxO, February 2, 2026 (see note 3).
Lichtenberg, Fortune, December 15, 2025 (see note 6).
Hulme, Digital CxO, February 2, 2026 (see note 3).
Deloitte, Tech Trends 2026 (see note 1).
Lichtenberg, Fortune, December 15, 2025 (see note 2).
The 93/7 split explains a lot of what I see inside large organisations. But "the technology is ready" is only partly true, and where it isn't true matters. In regulated industries the fundamentals are still unsolved: security, transparency, the ethics of the decision itself, and long-term provenance — where proof of a decision made by a machine has to be reproduced exactly, possibly years later, in front of a regulator or a court. The AI acts now arriving will test every one of these. The technology might work in a demo. Enterprise readiness is a different bar, and there is a seriously long way to go.
There is a second problem sitting underneath the investment imbalance. A large share of what is being done under the AI banner could have been done with existing, simpler technology. Workflow, rules, decent data plumbing. Not everything needs AI, and reaching for it by default is part of why so much of that 93% delivers nothing.
Then there is the receiving end of these systems. Take recruitment. AI screening is the biggest disaster going — capable people filtered out before a human ever sees them, no explanation, no appeal. If you want a proof point for why deployment without redesign fails, that is it. The organisation saved time, and the cost transferred to people who never agreed to the system, cannot see it, and cannot challenge it.
Reimagining how the organisation works has to include the people the system points at, not only the people operating it.