Sanjay Dudani
Home  /  Field guide

Analysis · Enablement & Adoption

How to run an AI enablement program for a large team.

Your people are already using AI. Whether that turns into value — or just risk — depends entirely on the enablement program around it. This is a field guide to building one that changes how a large organization actually works.

By Sanjay Dudani Independent analysis · enterprise AI Evidence-first · every figure sourced
The short answer

An AI enablement program is not a training catalog — it is the operating system that turns scattered, individual AI use into a capability the organization compounds. The evidence is stark: employees are already using AI more than their leaders realize, yet only 1% of companies are "mature" at it. The gap is enablement, not access. Closing it takes five moves — start from real workflows and a business owner, meet the adoption that already exists instead of fighting it, build role-based capability rather than generic literacy, design governance in as an enabler, and measure adoption depth and outcomes rather than attendance.

1%

of leaders call their companies "mature" on AI deployment — fully integrated into workflows and driving real outcomes.

McKinsey, AI in the workplace 2025

leaders underestimate employee AI use — they estimate 4% use gen AI for a third of their work; employees report three times that.

McKinsey, AI in the workplace 2025

~50%

of employees say more formal training is the single best way to boost adoption — yet over a fifth get minimal-to-no support.

McKinsey, AI in the workplace 2025

5%

of custom enterprise AI tools reach production; MIT names the barrier as organizational learning, not technology.

MIT NANDA, State of AI in Business 2025

Your people are already using AI. That's not the problem.

The instinct, when a large organization decides to "do AI," is to buy licenses and schedule training. Both are necessary. Neither is where the value is won or lost — because access and awareness are already solved. McKinsey's 2025 workplace study found that 94% of employees are familiar with generative AI, and that leaders underestimate how much their people already use it by a factor of roughly three.

So the real question is not how do we get people to use AI. They are using it. The question is whether that use is scattered, invisible, and occasionally risky — or organized, governed, and compounding into a capability. That difference is what an enablement program exists to create, and it is why only 1% of companies have reached maturity while nearly everyone has "started."

Employees are ready. Nearly half say more formal training is the best way to boost adoption — yet more than a fifth report receiving minimal to no support. Paraphrasing McKinsey, AI in the workplace: A report for 2025

Why AI training programs fail to change how people work

Five patterns — none of them about the content of the training.

Programs that spend real money and change nothing tend to share the same shape:

1. Generic literacy, detached from real work. A company-wide "intro to AI" teaches everyone a little and no one enough to change their actual job. Capability has to be built on the workflows people do every day, by role.

2. A one-off event with no reinforcement. A workshop is a moment; behavior change is a system. Without follow-through, practice, and support in the flow of work, people revert to how they worked before by the following week.

3. Fighting shadow AI instead of channeling it. Widespread unapproved use is treated as a threat to be banned rather than the clearest signal the organization has of where AI creates real value. Banning it forfeits the learning and drives it underground.

4. Measuring attendance, not adoption. Completion rates and license counts feel like progress but measure inputs. If no one asks whether the work actually changed, it usually hasn't.

5. Governance bolted on as a blocker. When risk and security arrive after the fact, enablement and compliance pull against each other. Designed together, guardrails are what let people move faster with confidence.

The five moves that build real capability

A sequence, not a curriculum. It is a change program, not a course.

Enablement at scale is an operating-model change. These five moves are what separate a program that shifts how an organization works from one that generates certificates.

1

Start from real workflows and a business owner

Anchor the program to specific, high-value workflows and to the business leaders who own the outcomes those workflows drive. Enablement that starts from "AI literacy" in the abstract goes nowhere; enablement that starts from "here is how this team's actual work changes" compounds.

2

Meet the adoption that already exists

Map what people are already doing with AI — including the unapproved tools — and treat it as your richest source of high-value use cases. Provide governed alternatives for the same jobs. You are not creating demand from zero; you are organizing and legitimizing demand that already exists.

3

Build role-based capability, not generic literacy

Design the depth by role: what a finance analyst, a support lead, and a marketer each need looks different. Generic training produces generic (near-zero) behavior change. Role-based capability, tied to the tasks a person actually owns, is what sticks.

4

Design governance in as an enabler

Bring risk, security, and legal in as co-designers so the rules ship as clear, usable guardrails rather than a late veto. People move fastest when they know exactly what is safe — governance done right is an accelerant, not a brake.

5

Measure adoption depth and outcomes, not attendance

Instrument the program for what matters: the share of people using AI for a meaningful part of their real work, the time and quality changes in named workflows, and the count of processes where AI is now the default. Reinforce what works, retire what doesn't, and report outcomes to the business owners from step one.

What a good enablement partner actually does

The work here is not delivering slides; it is designing an operating change and making it stick across a large, busy organization. A useful outside partner brings the sequence, adapts it to how this company actually works, and stays honest about the hard part — that enablement is measured in changed behavior, not attendance. The value is in having built the operating model and the governance before, and in being independent enough to tell you where your program will quietly fail if you don't fix it. Independence matters: advice on how your people should work with AI is only trustworthy when it isn't an argument to buy a particular platform.

Frequently asked

What is an AI enablement program?

The operating system that turns scattered, individual AI use into a capability the organization compounds — covering real workflows, role-based capability, governance, and the measurement of adoption depth and outcomes. Its goal is not that people have heard of AI, but that the way work gets done has changed.

Why do AI training programs fail to change how people work?

Because they treat enablement as a one-off event, not an operating change. McKinsey's 2025 report found 94% of employees already familiar with gen AI and using it more than leaders think, yet only 1% of companies mature — the gap is a system for reinforcing behavior and measuring adoption, not awareness or access.

How is AI enablement different from AI training?

Training transfers knowledge; enablement changes behavior at scale. Training is a workshop; enablement is role-based capability built into real workflows, supported by governance, reinforced over time, and measured by whether work actually changed.

How do you measure the success of an AI enablement program?

By adoption depth and business outcomes — the share of employees using AI for a meaningful part of their real work, time or cost saved in specific workflows, quality changes, and the number of workflows where AI is now the default. Completions and license counts are inputs, not results.

How should a company handle employees already using unapproved AI tools?

Channel it, don't just ban it. Widespread unapproved use is evidence of real demand and value; banning it forfeits the learning. Provide governed alternatives for the same jobs and fold what people are actually doing into the program as your highest-value use cases.

Turn scattered AI use into an organizational capability.

If your teams are already using AI but it isn't yet changing how the work gets done, the fastest first step is an honest read on where the enablement gap actually sits — and the sequence to close it.

Request a conversation

AI-Readiness Assessment — coming soon.

Sources

  1. McKinsey & Company, AI in the workplace: A report for 2025 (“Superagency in the workplace”), 28 January 2025. Findings cited: only 1% of leaders call their companies “mature” on AI deployment; leaders underestimate employee gen-AI use roughly threefold (estimate 4% vs. ~12% self-reported); 94% of employees familiar with gen AI; nearly half of employees say more formal training is the best way to boost adoption while over a fifth receive minimal-to-no support.
  2. MIT NANDA, State of AI in Business 2025 — The GenAI Divide (Jan–Jun 2025). Findings cited: only 5% of custom enterprise gen-AI tools reach production; “The core barrier to scaling is not infrastructure, regulation, or talent. It is learning.”