Measure your team's AI competency

The pattern repeats across almost every AI initiative that stalls: the tools were fine, the licences were bought, the town hall went well, and six months later usage has collapsed to a handful of enthusiasts. Post-mortems blame the tool. The honest answer is that nobody ever measured whether the people whose work was changing could actually work the new way, or wanted to.

Self-reported confidence is the worst instrument in the building. Ask people to rate their own AI skills and you measure enthusiasm and anxiety, not capability. What matters is applied skill: who actually uses AI in their real work, how well, and where the blockers sit. Measured properly and normalised, that picture is almost always surprising, and rarely matches the org chart's assumptions about who is ready.

The riskiest team in your organisation is the one whose work is changing fastest and whose readiness is lowest, and today you cannot name it.

The number that should worry a leadership team is not average fluency. It is the intersection: the teams whose work has the highest AI exposure and the lowest readiness. That intersection is where transformation risk concentrates, where capability spend pays back fastest, and where doing nothing is most expensive. Most organisations cannot name those teams today, which means their L&D budget is being sprayed evenly across a problem that is anything but even.

This programme builds the baseline that makes the intersection visible: real fluency and usage per team, mapped against where each role's work is heading, without turning measurement into surveillance. It is the difference between a training budget and a capability strategy.