May 11, 2026: Deployment Isn't Transformation. The Research Is Finally Clear on the Difference.
- James Sale
- May 12
- 6 min read
Updated: May 13
IBM replaced approximately 200 HR professionals with AI agents this month. The full function suite is live — recruiting, onboarding, benefits administration. This wasn't a pilot announcement or an aspirational roadmap slide. Confirmed production deployment in a major enterprise, running now.
At the same time, Cloudflare cut 1,100 people — roughly 20% of its workforce — with the company explicitly citing a 600% surge in internal AI usage over recent months as the operational context for the reduction. Oracle is working through a separate reduction of 20,000 to 30,000 jobs, redirecting the headcount spend toward AI infrastructure and data centers.
The decisions are made. The transitions are underway.
What's less settled is whether any of this goes well.
That's not pessimism. It's the consistent signal coming out of a wave of research published this spring. McKinsey, BCG, and Kearney each published independent findings pointing at the same variable: roughly 70% of what determines AI transformation success is people, process, and change management — not the technology itself. The model selection, the compute allocation, the vendor evaluation — all of that matters, but it accounts for the minority of the equation. Most of what determines whether AI deployment turns into actual organizational improvement sits in the management layer.
What the Adoption Research Is Actually Showing
Perceptyx sharpened that finding further. Their analysis of employee listening data found that trust in leadership is a stronger predictor of generative AI adoption success than technical proficiency or tool access. Not training depth. Not software quality. Trust.
That result has direct implications for anyone designing or sponsoring an AI rollout. It suggests the primary bottleneck in most organizations isn't tooling — it's credibility. Employees adopt AI faster and more thoroughly when they believe leadership is being straight with them about what's changing, why, and what it means for their role. Resistance patterns, Perceptyx found, tie more to perceived fairness and the quality of communication than to fear of job loss alone.
For companies deploying AI while simultaneously announcing large headcount reductions, that's a complicated starting position. IBM, Cloudflare, and Oracle are doing exactly that. The technology deployment may be technically sound. Whether the remaining workforce absorbs it productively depends on organizational dynamics that most AI vendors don't have a product for.
The practical implication is concrete: if your rollout plan allocates most of its management attention to the technology stack and treats communications as a downstream activity, the research suggests you're likely to underperform your implementation investment. The organizations getting consistent results are doing something different.
The Change Muscle Problem
BCG and Kearney's framing is worth spending time on. Their research describes what they call a "change muscle" — the organizational capability to absorb, adapt to, and continuously integrate new operating models. The companies performing best on AI transformation treat this as a permanent operational capability, not a one-time project. They've structurally embedded continuous transformation into how they run.
That's a different management challenge than selecting tools or setting AI adoption targets. It requires investment in change infrastructure — sponsorship structures, feedback mechanisms, reinforcement systems — that most organizations have never built because they didn't need them continuously. They built them for specific initiatives and then wound them down.
The Kearney finding is that winding them down is the mistake. The pace of change coming from AI deployment means transformation is no longer episodic. Companies that treat each AI initiative as a discrete project are building and dismantling change capacity repeatedly. The ones doing it well have stopped cycling through that.
Where the Production Results Show Up
Ciena's deployment of MoveWorks' agentic AI system is one of the cleaner case studies available at this scale. More than 100 workflows automated and running in production. Approval cycle times reduced from days to minutes in enterprise networking operations. Named company, specific outcomes, real production context — not a controlled pilot with carefully selected use cases.
What's notable about the Ciena example isn't just the efficiency improvement. It's how the deployment was scoped. Rather than a broad AI rollout across the organization, the implementation targeted defined business processes with measurable output cycles and clear decision points. Approval workflows are a natural fit: the inputs and outputs are structured, the handoffs are documented, and the time from submission to decision is straightforward to track.
That scoping approach makes results quantifiable and the business case defensible. It also makes change management more tractable — employees whose approval workflows changed can see the before and after clearly, which reduces the trust deficit that Perceptyx's research identifies as the primary adoption constraint.
The Salesforce Indicator
Salesforce now reports AI agents handle approximately 50% of customer service interactions. The company has built a formal program — "Managing at Salesforce" — specifically to train managers on leading mixed teams of people and AI agents. That program exists because the challenge is real: managing a hybrid team requires skills that aren't covered by traditional management development. Workflow oversight, output review, escalation protocols, and accountability structures all work differently when some of the team members are automated systems.
The 79% figure from Salesforce's workforce data carries weight beyond the company itself. Nearly eight in ten of their workers say they expect employer-supported reskilling as AI scales. That expectation is no longer limited to tech company employees or early adopters. It's spreading across industries as deployment accelerates, and it's shifting from a request into an expectation that affects hiring, retention, and engagement.
Organizations treating reskilling as optional or deferred are likely to see the cost show up differently — through attrition among the people they most want to keep, or resistance patterns that slow adoption of the systems they've invested in building.
The Strategy Layer Is Restructuring Too
What's happening inside companies is being mirrored by structural changes in the advisory industry around them.
Anthropic is in active discussions with Blackstone and Hellman & Friedman on a joint venture to embed Claude across their private equity portfolio companies. The model is explicitly Palantir-style: not a software license with an implementation partner, but deployed AI combined with integrated consulting services. The focus areas are financial analysis, software engineering, and customer operations — the same white-collar functions where most enterprise AI adoption is currently concentrated. Blackstone and Hellman & Friedman collectively have hundreds of portfolio companies. Successful execution would move Claude into professional functions at a scale that direct enterprise sales would take years to reach.
Bain & Company moved in a different direction toward the same goal. The firm formalized partnerships with seven major VC firms under a Venture Ecosystem program. The design gives Bain clients direct co-innovation access to AI startups — early visibility into what's being built and the option to co-develop before products reach the open market. The structure is about giving clients an advantage in identifying what's coming before competitors do.
Neither of these is an announcement about adding AI tools to a consulting practice. Both are structural shifts in how strategy advice gets packaged, delivered, and monetized. Consulting firms are positioning to own the transformation work, not just recommend it. For executive teams working with major advisors, that shift is worth understanding clearly: when the advisory firm's business model includes a stake in the deployment outcome, the nature of the advice changes. It's worth asking what that means for how recommendations get shaped.
The Question Under All of This
The technology decisions at IBM, Cloudflare, Oracle, Salesforce, and Ciena are largely made. The headcount restructuring is in motion. The PE and consulting firms are moving capital and partnerships to capture implementation value at scale.
The consistent finding across McKinsey, BCG, Kearney, and Perceptyx research is that the constraint separating companies that perform from companies that struggle isn't access to technology. It's the organizational infrastructure built around the technology — leadership credibility, continuous change capacity, and genuine investment in the people whose roles are being redesigned.
Companies building that infrastructure deliberately are producing results like Ciena's: specific, measurable, repeatable. Companies treating it as the soft layer that follows the real work are accumulating a change management debt that tends to come due right when they need adoption most.
If you want to stay ahead at the intersection of AI, automation, and human performance — where technology meets psychology, processes, and real workplace behavior — subscribe to Agenticism. We cut through the hype to deliver practical insights for leaders focused on making people, processes, and technology work better together.
