The Barrier to AI Adoption Isn't Technology.
It's Permission.
After I ran a two-hour live build session with my team, something happened that no training program had ever produced. People asked for access to the tools. Not because I told them to. Because they watched me use them on something real, and the gap between “that’s what tech people do” and “that’s something I could try” collapsed. The barrier to AI adoption in most organizations is not the technology. It’s not the budget. It’s the unstated belief that building is for someone else.
Most organizations approach AI adoption as a rollout problem. You introduce the tool, you run training, you track usage, you measure productivity gains. The assumption underneath all of it is that the gap is informational. People don’t know how to use AI, so you teach them. Then they will use it.
That framing is wrong. Or at least, it’s incomplete.
What actually keeps people from building with AI isn’t a knowledge gap. It’s a permission gap. A sense that experimentation is allowed, but building is reserved for people with different job titles. The people in corporate functions, HR included, have been trained for years to be good consumers of technology and to leave the building to engineers and product teams. That muscle memory doesn’t get overwritten by a lunch-and-learn.
What does overwrite it is seeing someone in your own orbit, not a vendor, not a consultant, not a keynote speaker, build something real. When I shared my screen and worked through problems live, I wasn’t just demonstrating a tool. I was demonstrating that it was possible. For them. In their context. With their problems.
The requests for access to new tools came within days. The ideas that followed weren’t “here’s what we could ask IT to build someday.” They were “here’s what I want to try next week.” That’s a different kind of sentence. It signals ownership.
HR leaders talk a lot about building AI capability across their organizations. Most of the interventions that follow look like training programs. Those programs have their place. But they are building informed consumers, not builders. And informed consumers are one budget cycle away from disengagement when the tool changes or the ROI doesn’t materialize fast enough.
Builders stick. Builders iterate. Builders pull others in.
If you are the only person on your team who builds AI tools, you are not ahead of the curve. You are a bottleneck with a good story.