Your team's AI problem isn't a skills gap. It's a visibility gap.
Most companies cannot say how AI-fluent their teams are because they measure access and activity, not fluency. Self-report and certificates hide your real risks. Fluency is role-shaped, so a single company-wide readiness score is useless. Measure the outcome, role by role, before you spend another rupee on training.
We measure everything except the thing changing fastest
Every leader I talk to has the same quiet worry about AI. Not the dramatic one from the headlines about machines taking the jobs. A smaller, more uncomfortable one: I genuinely do not know if my people are any good at this.
They have bought the licences. They have run a training session. Someone forwarded the vendor's best-practices deck around the company. And yet, if you ask that same leader how AI-fluent their finance team is compared to their sales team, the honest answer is a shrug.
That shrug is the whole problem. And it is not a skills problem. It is a measurement problem. We track revenue per head, pipeline coverage, attrition and customer satisfaction. But whether a person can get useful, trustworthy work out of AI is tracked by vibes: a show of hands in the town hall, or a course-completion certificate that proves someone watched a video, not that they can use the tool when it counts.
Self-report cannot measure this, and certificates are worse
Ask people to rate their own AI ability and two groups quietly break your data. The confident-but-wrong, who are sure they are power users and are actually pasting sensitive data into a chatbot and shipping its first answer. And the capable-but-modest, who are doing genuinely clever things and would never say so on a survey. The first group is your risk. The second is your hidden leverage. Both are invisible to a self-assessment.
A survey hides exactly the two groups you most need to see.
Fluency is not one number. It is role-shaped.
What good at AI means for a customer-support lead has almost nothing in common with what it means for a financial analyst, a designer, or a recruiter. A single company-wide AI readiness score averages all of that into a figure that is true of no one and useless to everyone. The differences you flattened are the exact differences you needed in order to act.
Access, activity, fluency: the three levels leaders confuse
There are three levels here, and most companies mistake one for another:
- Access: your people have the tool. This is a procurement fact. It tells you nothing.
- Activity: your people are using the tool, measured in logins, prompts and tokens. Most AI adoption dashboards stop here, and this is where leaders fool themselves.
- Fluency: your people get a better outcome, faster, that they can trust and defend. This is the only level that shows up in the business.
A team can be enormously active and barely fluent. Busy is not the same as good. If your dashboard measures motion and calls it adoption, you are counting the wrong thing.
You cannot train what you cannot see
This is not an academic distinction. It is a budget one. Blanket AI training is the single most expensive way to upskill a company, because you spend the same amount on the person who is already a multiplier and the person who needs a completely different first step. When you cannot tell those two people apart, you overpay for one, underserve the other, and learn nothing about which was which. Measure first, and the training pays for itself, because you finally aim it.
The companies that win the next two years will not be the ones that adopted AI earliest. Everyone adopted AI. They will be the ones who could see, role by role and person by person, who was actually getting value from it and who was quietly stuck, and who then did something specific about it. That visibility is the entire reason we built AI Litmus.
Stop asking your people whether they are good at AI. Start looking at whether the work got better.
See this on your own teams.
A private walkthrough, calibrated to your roles. About two weeks.
Frequently asked
How do you measure AI fluency in a team?
Not with a self-assessment or a certificate. You measure fluency by looking at the actual work: whether a person gets a better, more trustworthy outcome, faster, on the tasks their specific role involves. That means observing real usage against role-relevant tasks rather than asking people to rate their own confidence, and reading it per role rather than as one company-wide score.
Why are self-assessments and certificates not enough for AI skills?
Self-assessments hide your two most important groups: the confident-but-wrong, who overestimate their ability and create risk, and the capable-but-modest, who under-report real skill. Certificates prove someone completed a course, not that they can apply it in their job. Neither tells you whether the work actually improved.
Is a single AI readiness score enough for a whole company?
No. AI fluency is role-shaped: what it means for a support lead is different from what it means for an analyst or a designer. A single company-wide score averages those differences away, so it is true of no one and gives you nothing to act on. A useful read is calibrated to each role.
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.
Connect on LinkedInOccasional, high-signal notes on measuring AI fluency and culture cost. No spam.