GenAI Transformation Is Not a Tool Rollout
Most GenAI programs fail not because the technology doesn't work, but because organizations treat adoption as an IT problem. It isn't.
Organizations are discovering a pattern. They buy a GenAI platform. They run access. Usage is low. Leaders ask why. IT says the tool is deployed. L&D says training was delivered. Nobody has changed how they work.
This is not a technology problem.
Why GenAI adoption stalls
GenAI tools change the nature of work, not just the tools used to do it. A copilot doesn’t just help a manager write faster — it changes what a manager is supposed to do. Decisions that used to take a day can take an hour. That means the volume of decisions required is now higher. The nature of judgment changes.
When organizations treat GenAI as a tool rollout — a series of training sessions followed by access provisioning — they are solving for awareness, not adoption. Awareness does not change behavior. It creates the appearance of a program while the actual work continues exactly as before.
What genuine adoption requires
1. Leaders who understand the shift, not just the tool
The most important variable in any GenAI transformation is whether the leadership layer genuinely understands the shift. Not “GenAI can summarize emails” — but “the role of a manager in a GenAI-enabled team is fundamentally different from what it was two years ago.” That understanding is almost never present from a vendor demo.
2. Use-case clarity before platform choice
Most organizations choose the platform first, then try to find use cases that justify the choice. This produces fragmented adoption. Genuine transformation starts with: what specific decisions, workflows, or outputs do we want to change? The tool selection follows from that.
3. Role-level behavioral change, not just awareness
Adoption happens at the individual level — when a specific person in a specific role changes how they do a specific task. Getting there requires knowing what the “before” behavior is, what the “after” behavior should look like, and what’s blocking the shift. Generic training cannot do this.
4. Leadership sponsorship that is active and visible
Employees watch what leaders do, not what the intranet says. If a VP continues to produce outputs the same way they always have, the message sent — regardless of any GenAI communication campaign — is that the change doesn’t apply to people like them.
5. Measurement of adoption, not just access
Access is not adoption. The right measurement question is not “how many employees have licenses?” but “how many employees have changed a specific behavior in a specific context, and what is the evidence?”
What this looks like in practice
At Amdocs, the GenAI transformation work included co-leading the design of an organization-wide transformation roadmap, designing strategic offsites for VPs and above to engage with the shift at a leadership level, and building an AI agent for change advisory that gave leaders real-time support on navigating the change — not generic awareness content.
The result was a change program designed around behavior, not technology. That is the only design that produces lasting adoption.
The question to ask before you start
Before designing any GenAI transformation program, ask: Is our leadership layer ready to model new ways of working, or are we trying to change employee behavior while leadership behavior stays the same?
If the honest answer is the latter, start with leaders.
Vaibhav Jayaswal leads OD and change for Amdocs and is the founder of Blue Feather Performance Consulting.