Buying tools is not the same as adopting them
Most AI budgets are spent on access: licences, seats, platforms. But access is not adoption. A seat that logs in once a month is a cost, not a capability. And the gap between what you bought and what people use is usually invisible, because nobody is measuring it at the level of the actual work.
When you look closely, the adoption gap almost always has two distinct halves, and each points to a different fix.
The two halves of the gap
1. Available but unused
Tools you already pay for that people should use but do not. Sometimes they do not know the tool exists. Sometimes they tried it once, hit friction, and quietly went back to the old way. This half is often pure recoverable value: the licence is already bought, so closing the gap is a training and enablement problem, not a spend problem.
2. Used but not good enough
Tools people use every day but have quietly outgrown, or that never fit the workflow well. This half tells you where a better tool, or a better setup, would actually move output. It is the opposite signal: here, more enablement will not help; a different choice will.
The adoption gap is the insight. Your next rupee of AI budget should go to the gap that actually moves output, not to another licence nobody asked for.
How to surface it honestly
You cannot find this gap in a licence dashboard, because usage counts do not tell you why. You find it by asking people about their real workflows: what they do each week, which parts AI could take, which tools they have, and where those tools fall short. Done privately and at the level of the actual job, this surfaces both halves of the gap at once.
- The unused-licence half becomes an enablement plan for tools you already own.
- The outgrown-tool half becomes a sharper procurement decision.
- Both together become an ROI case built on real workflows, not vendor claims.
Our AI Litmus module surfaces the adoption gap for every team as part of the fluency read, so you can redirect spend to where it actually pays off.
See this on your own teams.
A private walkthrough, calibrated to your roles. About two weeks.
Frequently asked
What is the AI adoption gap? The AI adoption gap is the distance between the AI tools an organisation pays for and the value employees actually get from them. It has two halves: licences that sit unused, and tools people use but have outgrown. Closing it means redirecting budget and enablement to where they will actually move output.
Why do employees not use the AI tools we bought? Usually because they do not know the tool applies to their work, they hit friction early and reverted to the old way, or the tool does not fit their actual workflow. A workflow-level conversation surfaces which of these is true for each team, which turns unused licences into recoverable value.
How do you measure AI ROI from tools already purchased? Start from the real workflows: the hours a tool could unlock, how many people would realistically adopt it, and how much of that theoretical saving becomes real value after verification and rework. Grounding the estimate in actual work, rather than vendor benchmarks, produces an ROI case that finance can check.
Shobhit Khandelwal
Founder, VMS Culture Labs
Shobhit Khandelwal is the founder of VMS Culture Labs, on a mission to measure what most leaders only guess at: how fluently their teams truly work with AI, and the hidden cost of how people behave at work. He is out to replace workplace guesswork with evidence, and build the kind of workplaces the next generation deserves.
Get the intelligence briefing
Occasional, high-signal notes on measuring AI fluency and culture cost. No spam.
Keep reading