Stop Measuring AI Adoption by Licence Activation

Activation and prompt counts measure access and curiosity. Leaders need evidence that AI changes valuable work.

2 minute readBy Lucas North

Licence activation is an attractive metric because it rises quickly, fits neatly on a steering-committee slide and is easy to report. It is also weak evidence that an AI investment is working.

An activated user may try three prompts, receive an indifferent answer and never return. A high prompt count may represent genuine value, repeated correction of poor output or recreational use. Activity tells you that the tool is available. It does not tell you that work improved.

Measure a job, not a feature

Choose a small number of important, repeatable jobs: preparing an account review, triaging a case, drafting a technical proposal or finding evidence for a control. Establish the current time, quality, failure rate and number of hand-offs.

Then measure whether assisted users complete that job differently. Useful signals include accepted outputs, verified time saved, reduced rework, faster cycle time and fewer escalations. Pair quantitative data with observation; users often relocate effort rather than eliminate it.

Distinguish reach, habit and value

A balanced adoption view has three layers:

  • Reach: who has access and has tried the capability?
  • Habit: who repeatedly uses it for a defined job?
  • Value: does that job produce a better outcome?

These layers diagnose different problems. Low reach may need communication. Weak habit may indicate poor workflow fit. High usage with low value may mean the tool is engaging but economically irrelevant.

Protect credibility

Do not manufacture a return-on-investment figure by multiplying self-reported minutes saved by every licensed employee. Use conservative samples, verified workflows and fully loaded costs. Include review time, integration, support and governance.

Executives do not need a larger adoption number. They need evidence that AI changes performance in specific work, and the discipline to stop funding it where it does not.

Written by

Lucas North

I build enterprise software and write about the decisions, constraints and failure modes that rarely fit into a product announcement.

More about me →