Gallup published workforce data recently that should be uncomfortable reading for anyone in a technology leadership role. Most American workers use AI tools only a few times a year. Nearly a quarter of employees do not know whether their organization has adopted AI at all. And among those who do use AI at work, a significant portion report that they received no guidance, no training, and no clear direction from leadership about how or when to use it.
I want to be direct about what this data tells us. This is not a technology problem. The tools exist. They are accessible, increasingly affordable, and in many cases already licensed by the organizations whose employees are not using them. The gap is not in the technology layer. The gap is in the leadership layer.
When employees do not know whether their organization has adopted AI, that is a communication failure. When they have access to tools but no guidance on how to use them, that is a strategy failure. When adoption rates are low despite significant investment, that is an execution failure. All three of these are leadership problems, not technology problems.
I have seen this pattern repeatedly in my work with associations and nonprofits. An organization invests in an AI-enabled platform, sometimes at significant cost, and then treats deployment as the finish line. The technology is installed. The contract is signed. The project is closed. And then, six months later, adoption is low, the team is frustrated, and leadership is wondering why the investment is not paying off.
The answer is almost always the same. The technology was deployed, but the change was not led.
Leading an AI adoption is not the same as deploying an AI tool. Deployment is a technical event. Adoption is a human process. It requires leaders who can articulate why the technology matters, not in abstract terms about efficiency or competitive advantage, but in concrete terms about how it changes the work that specific people do every day. It requires managers who model the behavior they want to see, who use the tools themselves, who create space for experimentation and normalize the learning curve. And it requires an organizational culture that treats not knowing how to use a new tool as a temporary state to be addressed, not a personal failing to be hidden.
The Gallup data also points to something more specific: the employees who are using AI most effectively are not necessarily the most technically sophisticated. They are the ones who have a clear mental model of what the tool is good for, who have been given permission to experiment, and who have a feedback loop that helps them improve. That mental model and that permission structure come from leadership. They do not emerge spontaneously.
If you are a technology or operations leader looking at low AI adoption in your organization, I would encourage you to resist the temptation to solve it with more technology. A better platform will not fix a leadership gap. More features will not fix a communication gap. What will fix it is leaders who take ownership of the adoption process with the same seriousness they brought to the procurement process, and who understand that the work of getting people to actually use a tool is harder, and more important, than the work of selecting it.