The AI Adoption Gap Isn’t About Access. It’s About Play.

My wife sat down with Claude to do some data analysis for work. She’d heard it was good with spreadsheets. Real project, real data, real deadline.

Her first attempt wasn’t even close.

So she tried again. Closer this time, but it grabbed too much — pulled in a term that looked similar to what she needed but shouldn’t have been in the analysis. Wrong bucket. Close enough to fool a casual glance, specific enough to matter.

A few more rounds. Each time she refined what she was asking for, the output got tighter. She started reading the results more carefully — not just checking if it worked, but understanding why it worked or didn’t.

By the end, she had what she needed. And for the first time in months, she was genuinely curious about what I do every day when I head down to the basement office.

She played with it — failed, adjusted, played again. And in that process, something clicked. Not just about the tool, but about the possibilities.

That’s not a training story. That’s a play story.

The data on AI adoption looks impressive until you read the fine print.

McKinsey’s 2025 State of AI survey found that 88% of organizations now report using AI — up ten points from the year before. Sounds like the gap is closing.

Except only 7% have actually scaled it. Two-thirds are still in pilot mode. And only 39% report any measurable impact on the bottom line.

Microsoft’s 2024 Work Trend Index tells a similar story from the individual side: 75% of knowledge workers say they use AI at work. But 78% of them are bringing their own tools — personal subscriptions, not company-provided. They’re using what they found by messing around on their own time.

Here’s the stat that should haunt every executive: only 39% of people using AI at work have received any training from their company.

Here’s the part that should make that stat sting: the adoption window is compressing faster than any previous technology shift. Railroads took twenty years to justify the investment. Fiber optics took ten. AWS took six. The current AI infrastructure cycle? Roughly eighteen months. The gap between early and late is getting shorter, and “I’ll figure it out next quarter” is a riskier bet than it sounds.

So the picture is: almost everyone has access. Almost no one has been taught. And the people who are actually good at it? They taught themselves — by playing.

The standard diagnosis for the adoption gap is access, training, or strategy. The data doesn’t support any of them. Access? Nearly universal. Training? Barely correlates with fluency. Strategy? Documents don’t make people better at prompting.

The real gap is between people who gave themselves permission to experiment and people still waiting for someone to tell them it’s okay.

This isn’t just anecdotal. The research on how adults learn novel technology is surprisingly clear — and it favors tinkering over instruction.

People who tinker with new software make more errors at first — but develop deeper mental models and transfer skills far more effectively than those who follow manuals. IBM researchers figured this out in the ’80s. It still holds. The messy early phase wasn’t wasted time. It was the foundation of fluency.

Nothing lights up the brain like play. That’s not metaphor — it’s neuroscience. Stuart Brown, a psychiatrist who’s studied play across 6,000+ life histories, explains why: when you’re playing, you’re in a state of open-ended exploration — trying things because you’re curious, not because you’re following a syllabus. You’re building intuition, not just knowledge.

The key insight: play reduces the cost of failure. When my wife’s first prompt didn’t work, she wasn’t stressed — even though it was for a work project. She was curious. Huh, that didn’t work. Let me try it differently. The task was work, but her approach was play. That distinction matters. If she’d been following a manual or sitting in a training session, that same failure might have been discouraging enough to quit.

Ethan Mollick at Wharton has been making this case for two years: there is no substitute for trying AI yourself. Reading about it is not enough. Watching demos is not enough. You need to use it, and you need to use it for things you care about.

Not things your company tells you to care about. Things you care about. That’s the difference between training and play.

If play is the answer, why isn’t everyone playing?

Because play requires something most organizations systematically crush: the safety to fail.

Amy Edmondson’s research found that psychological safety — the belief you won’t be punished for mistakes — is the single strongest predictor of high-performing teams. People experiment when they feel safe failing. They wait for instructions when they don’t.

Carol Dweck maps the same terrain from the individual side. The person who thinks “I don’t know how to use this yet” will play. The person who thinks “I’m not a technical person” will wait. The difference isn’t skill. It’s orientation.

Now look at how most organizations have approached AI. Risk assessments. Approved tool lists. Mandatory training. Compliance requirements. Every signal says be careful. Every process says wait for permission.

No wonder 78% of AI users are bringing their own tools. The tinkerers aren’t waiting.

This is the same pattern we’ve seen with every technology wave. Before Slack was officially approved, teams were already using it. Before ChatGPT was on the approved vendor list, people were pasting work problems into it at home. The people who adopt technology first aren’t more technical. They have a higher tolerance for acting without permission.

But here’s what matters for leaders: this isn’t just an individual trait. It’s an environmental one. Some organizations create conditions where play happens naturally. Others make it nearly impossible.

And there’s an equity dimension worth naming. Knowledge workers with autonomy can experiment without scrutiny. Front-line workers, those in regulated industries, those with less job security — they can’t afford to “play” at work. The permission gap maps to existing power structures.

“Just play with it” isn’t equally available advice. Which is exactly why creating the conditions for play is a leadership responsibility, not just an individual one.

I should be clear: play doesn’t mean chaos. And sandboxes aren’t just about protecting data — they’re about making play accessible to the people who can’t afford to experiment unsupervised.

The best organizations don’t choose between control and experimentation. They create bounded spaces where play is safe — tools with data guardrails, internal instances where a bad prompt costs nothing. As Tim Brown at IDEO has argued, play is not anarchy — it has rules, especially when it’s in the service of innovation.

And play alone isn’t enough. A Harvard/BCG study of 758 consultants found that people who blindly followed AI output actually performed worse than people without AI at all. That study is from 2023 — ancient in AI years. But the finding holds: tools outpace judgment unless you develop the judgment through experience. Play without reflection is just entertainment. The real learning comes from the full cycle: try something, notice what happened, adjust, try again.

My wife didn’t just retry the same prompt. She noticed what went wrong — the mismatched term, the too-broad dataset — and adjusted her approach. That’s play plus reflection. That’s how fluency develops.

If you lead a team or organization:

Stop building training programs. Start building playgrounds.

Provide AI tools with appropriate data boundaries. Give people genuine unstructured time to experiment — not a workshop, real time. Reward curiosity, not just compliance. Make it safe to share failures. Stop treating AI adoption like a risk to manage and start treating it like a capability to develop.

The McKinsey data is clear: the organizations capturing value from AI have cultures that encourage experimentation and bottom-up adoption. Not the best strategy decks.

If you’re an individual:

Stop waiting for permission.

Open Claude or ChatGPT tonight. Not for work — for something you actually care about. Plan your next trip without opening ten browser tabs. Figure out where your money actually goes each month. Write a bedtime story for your kid where they’re the hero.

See what happens.

It will feel clumsy. Your first prompt will be too vague, or too specific, or just plain wrong. You’ll stare at the output and think that’s not what I meant at all. Good. That’s exactly what my wife felt at the kitchen table — and it’s the feeling right before the thing clicks.

The gap between your first prompt and your tenth is where fluency lives.

The people on the other side of Roose’s gap didn’t get there through training. They got there by playing. And the distance between those two sides is growing faster than most people realize — not in years, but in months. It always started the same way: one evening, one question they actually cared about, one screen glowing on a kitchen table. Tonight could be yours.

— -

I build AI agents and write about the human side of working with them. If you’re navigating this gap — from either side — I’d like to hear what you’re seeing.