Score
← Decisions · Justify the AI spend · The board conversation

The board wants to know what the AI investment is returning. Usage data will not close that question.

Licence costs and adoption percentages measure whether tools are present and whether people have opened them. They do not tell you whether the organisation is better at anything that matters.

The gap the board is pointing at
The question is capability, not cost.

The question the board is asking is not: how much did we spend, and who used it? The question is: are we more capable than we were, and can we show it? These are not the same question and usage data does not bridge the gap between them.

A high adoption rate is consistent with an organisation that has automated low-value tasks and left high-value judgment work exactly as it was before. That is not a return. It is a cost with a visible dashboard. The board meeting ends with no answer because the organisation has been measuring the wrong thing.

What the board is actually asking about sits between two things that are genuinely hard to measure: whether AI is being applied where it multiplies value rather than just reduces cost, and whether the human capability that makes performance sustainable is growing or quietly contracting. Neither shows up in a licence report.

What the score measures instead
Nine dimensions. Two readings that matter for the board.

The Kaivant Score reads nine dimensions across two axes: what the organisation can currently produce with AI, and whether the human capability required to sustain that is growing or contracting. For the board conversation, two readings matter most.

The first is Leverage Trajectory: whether AI is applied where it multiplies value across the organisation, not just where it saves time. A high adoption percentage with a declining Leverage Trajectory means tools are busy and impact is flat. A low adoption percentage with a rising Leverage Trajectory means the organisation is deploying selectively and building capability. These tell opposite stories, and only one shows up in the current reporting.

The second is Capability Development Velocity: whether the people doing the work are more capable than they were before the deployment. This is the question the board is implicitly asking when it asks for a return on investment. An organisation substituting AI for human judgment rather than augmenting it will show flat or declining CDV. That reading is the answer the board needs, whether or not the number is comfortable.

What happens next
A score is a starting point. What the board wants is a direction.

A single Kaivant Score is the current state. What the board is asking for, implicitly, is evidence of a trajectory: that the reading will be better in six months than it is today, and that there is a named person and a named action behind that expectation.

The facilitated session is the step between the score and that commitment. The leadership team reads the score together, identifies the two or three dimensions pulling the result down, agrees the smallest first move for each one, and names the date of the next measurement. The next board conversation opens on the delta: what the reading was, what moved, and why.

The developmental loop

Score the current state · Diagnose which dimensions are creating the drag · Act on two or three specific moves · Re-measure and compare the delta. That is the answer the board is asking for.