
I’ve been reviewing Wharton’s latest AI adoption report, and I’m curious about one finding in particular. Managers and above were far more likely than entry and mid-level employees to say employees receive adequate AI training. It made me wonder how many AI fluency plans are, in practice, just course catalogs.
Courses matter, of course. What I’m less sure of is how much a course can do for someone who goes back to a team where nobody has time to try things and a good idea has no clear pathway to change formal ways of working.
What the study says about AI training and its effectiveness
The report, The Adaptive Advantage: Who’s Winning With AI and How from Wharton Human-AI Research and GBK Collective, surveyed about 1,400 people at US enterprises with 1,000 or more employees and more than $50 million in revenue. Most of the leaders in it like what they’re seeing so far. Eighty percent of managers and above report a positive return from AI, and 28% call it strongly positive. Yet only 7% of organizations clear all three of Wharton’s markers for success: proving value, transforming workflows, and aligning the organization.
On training, 78% of managers and above agree that employees receive adequate AI training. Among entry and mid-level employees, the figure is 56%, the largest gap of any readiness measure in the study. And 65% of managers and above agree that what holds their department back with AI is mostly people and processes.
I want to be careful with this because it is self-reported survey data, so it tells us what is associated with success, not what causes it. Adequate training is one of Wharton’s five alignment factors, so the report does not say training is a waste. It counts training as one factor among several. Wharton calls the organizations pulling ahead adaptive, and defines an adaptive organization as “one that rebuilds how its work gets done around AI and brings its people along with it.”
Where AI enablement grinds to a halt
In my experience, individual skill with AI is rarely the bottleneck. Most teams already have a few people who are very good with these tools. The trouble is that what they know stays with them as individual intellectual capital and has a hard time spreading to others.
Then there’s the route from a working prototype tool to everyday use. A vendor-published customer story on LangChain’s blog describes how things used to go at Workday, where “building a prototype agent took 4 to 5 months, with no guarantee it could ever reach production.” Workday then built an internal platform that handles authentication, security, compliance and infrastructure, so teams could focus on what the agent needed to do, not necessarily how to do it. According to the story, a team can now have a prototype running in a staging environment in under a day.
In my experience, building a platform like this is out of reach for most teams. The more important part of Workday’s story is why it got faster. Someone treated the path from idea to production as something worth transforming. When nobody designs that path, a capable person finishes the course, builds something useful, and then watches it sit in review for a quarter.
My read is that AI fluency spreads when people have dedicated time to experiment, a shared practice to draw from, and a clear path from prototype to daily use. A curriculum can’t supply any of that on its own. You can design those conditions, the same way you design a product.
Designing the conditions for AI fluency to shift the org.
If experimenting with AI is something people do after their real work, it mostly won’t happen. It needs protected time on the calendar, ideally with a teammate. Then tie it to an actual task from that week rather than a practice exercise in a vacuum.
Shared practice keeps every team from starting over. On a How I AI episode published on Lenny’s Newsletter, Figma PM Ezra Mechaber describes PM OS, a shared repo of 31 skills that every PM at Figma now uses. (A skill, in this sense, is a saved and reusable set of instructions for an AI tool.) The repo matters less than the habits surrounding it. It started as Mechaber’s personal setup, and now 60-plus PMs start from there. That’s how AI fluency moves past the few people who had it first.
The route out of the sandbox needs designing too. Teams should know how an experiment becomes an approved tool: who reviews it, what the reviewers look for, and roughly how long it should take. Governance also controls how fast a shared library grows. Teams have to decide how broad a shared skill should be. Broad skills cover many scenarios with some flexibility and keep the library small and manageable. Narrow skills fit one use case and can be more accurate, but they pile up into an app store nobody can browse. The backend processes and governance deserve the same research and design attention as anything a customer touches.
What to measure instead of completions
All of this is hard to see if the only thing you track is training completion. Completion rates tell you how many people sat through a module. They tell you nothing about whether a claim gets resolved faster or a monthly report needs fewer handoffs. NN/g’s guidance on establishing baselines makes the point that one of the most common ways UX teams undermine their own value is by measuring too late. Take a before-measurement on the actual workflow, before anything changes. Without it you can’t show that AI did anything. That makes a pilot that worked very hard to defend at budget time.
Where we start at Grand
Most of our AI work starts as research into how people actually do their job or how customers are engaging with a brand. For a quality team at a global manufacturer, that meant interviews and surveys with roughly 2,500 internal users to learn which proposed features would change their work and which only looked useful. We made the case for cutting the second group. For the AI itself, we designed the interface to show the risk and rationale behind what an agent was doing, not only its output, so reliance could match what the system could actually do, which is what we call calibrated trust. We started from how the work actually gets done, and the AI fit inside that.
At Grand, we believe people get fluent with AI inside work they’re allowed to change. So the work and its processes are what we redesign first, transparently and with the people who do it, and so AI has a baseline to prove its value against.
If you’re trying to get AI fluency to spread past the few people who already have it, we’d like to hear what you’re building, and we’d be glad to look at the workflow with you. Bring any in-progress ideas. Let’s connect