Ask a public leader what share of their workforce uses artificial intelligence at work each week. The answer is almost always an estimate. Sometimes a generous guess. Rarely a measured figure.
That would be a detail were the next decision not, invariably, an investment. A platform, a training programme or a consultancy is procured on the basis of a perception, and twelve months later the result is assessed on the basis of another perception. Between the two there is nothing comparable.
What a proper diagnostic reveals
A simple instrument, applied across the whole workforce, tends to reveal four things nobody anticipated.
- Real adoption is higher than leadership imagines, and it is concentrated in unapproved tools.
- The stated bottleneck is almost never the real one. Where cultural resistance is assumed, a training gap is found. Where a lack of interest is assumed, insecurity about what is permitted is found.
- Managers and non-managers face different barriers. Treating both groups with the same action wastes half the effort.
- Appetite for learning grows faster than the supply of training. When that happens, the people development function becomes the bottleneck, and is usually the last to know.
The cheapest diagnostic in the programme tends to be the one that prevents the most expensive contract.
Why measurement has to recur
A single measurement produces a photograph. Two measurements produce a direction. It is the second that allows a budget to be defended, because it converts a statement about intention into a statement about results.
An organisation that measures adoption every six months can state, with evidence, that the share of staff using AI at work rose by a given number of percentage points, that the sense of insecurity fell, that the perception of real productivity gain moved up a band. None of those statements survives without the previous measurement.
What to do with the result
A diagnostic that ends in a report is of no use. What changes an organisation is the executive read-out: the session in which senior leadership sees the dashboard, recognises the real bottleneck and leaves with three prioritised moves, each with an owner and a deadline.
Three moves. Not fifteen recommendations. The difference between a diagnostic that generates action and one that generates an archive lies almost always in the discipline of reducing the recommendation to what the organisation can execute in the next quarter.