In many boardrooms, the conversation about AI sooner or later turns to pace. One board member wants to accelerate, another wants to slow down, and no one can point to exactly where the difference in view comes from. That's not because people don't want to agree. It's because there is no shared picture of where the organization currently stands. Without that picture, every position on pace is an opinion, and opinions are hard to reconcile. Why your executive team disagrees about AI pace describes this pattern in more detail; this page is about the approach that does something about it.
The maturity measurement from hybridresourcing does not set one opinion against another. It places seven dimensions side by side — including organization, IT infrastructure and data management — and determines a level for each dimension: baseline, foundation, activation, insight or intelligence. That does not produce a judgment about ambition, but a description of where the organization currently stands, dimension by dimension.
The most important part of this is the order. The fundamental dimensions come before the dependent ones, not because that's a preference, but because that is the order in which it works. An organization that is still at baseline level on data management cannot reach activation level on a dependent dimension, however much the board might wish it could. The measurement makes that dependency visible instead of assuming it.
The part that changes the pace conversation the most is the plot round. Multiple people from the organization — board, executives, and often also people who actually carry out the work — score the same seven dimensions separately from each other. Only afterward are the scores placed side by side.
What then becomes visible is spread. Not one figure, but a range of assessments that diverge, and those differences are exactly where the conversation normally gets stuck already. If the CEO estimates the data management dimension at insight level and the CIO at foundation level, that difference is no longer just an atmosphere in the meeting. It is a figure that calls for explanation. Why does one score higher than the other? What assumption lies beneath that? The plot round shifts the conversation from pace to assumptions, and assumptions can be tested.
The measurement does not determine pace. It does not produce tailored advice, no recommendation about what the organization should do now, and no prediction about how long it takes to move from one level to another. That depends on too many factors the measurement does not know — sector context, available capacity, prior investments — to make a statement about it that is more than guesswork.
The measurement also guarantees nothing about outcomes. A high score on a dimension says something about the current state, not about what the organization will do with it or what that yields. And the measurement is a snapshot; it ages. How often a maturity measurement needs to be redone addresses the question of how long a score remains valid, and the answer is: shorter than board members often expect, especially for organizations that have only just begun to change.
What the measurement also does not do is make the conversation unnecessary. It moves the conversation to a place where it is more productive, but the board and the executives still have to conduct it themselves — with each other, about the spread that the plot round exposes.
A low score on one of the fundamental dimensions is not a negative judgment. It is a description of where the organization stands, and that description calls for a decision: build first, or proceed anyway despite the risk. Which two scenarios go with a low score explains which two routes are open in that situation, without presenting one as better than the other. That is also why this measurement does not give advice: which route fits is a judgment call that lies with the organization itself, not with an instrument that only measures.
It is worth keeping the distinction sharp here between what this measurement does and what it does not do. What the difference is between AI supporting and AI taking over makes that distinction explicit: this measurement is about capacity to bear, not about which tasks AI could take over. Anyone who looks only at a chat window to determine whether the organization is ready misses most of what still needs to be in place — what you don't see if you only know the chat window shows what falls outside that.
The maturity measurement, including the plot round, is still under development. Anyone who wants to use something of this already can join the waiting list; there is not yet an instrument ready today to fill in. If you want to know in advance how mature your organization currently appears, how mature your organization is when it comes to AI gives an initial indication, without the precision of the full measurement.
Once it is clear whether the organization can bear AI, a separate question remains open: what AI can actually take over within that organization. That is a different measurement, with a different scale. The work scan from FTE TO AI calculates per task which part of the work can be taken over by AI, based on the tasks as they are currently carried out. Where this page is about readiness, the work scan is about content — and both answers are needed before the pace conversation truly becomes concrete.
Vraag maar wat er moet staan voordat AI in uw organisatie kan landen.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.