Anyone who receives a score for the first time on the five levels — baseline, foundation, activation, insight, intelligence — then asks a different question. Not: what does this mean, but: how long does this remain true. A score is a snapshot. The organization does not stand still. The question about the repeat frequency is therefore justified, and the answer is less simple than a fixed interval of six or twelve months.
A maturity measurement registers a state on seven dimensions. Some of these change slowly. Data management, for example, does not shift within a quarter — that requires structural choices that take time to become visible in the score. Other dimensions can move faster. If the organization implements a leadership change, or if a decision is made about data governance, that changes the outcome on that specific dimension sooner than a year. A fixed repeat schedule treats all dimensions as moving at the same pace. They do not. You can read more about that order and why certain dimensions must come first in why the fundamental dimensions must come first.
The value of repeating does not lie in confirming a number. It lies in making movement visible, or the absence of it. An organization that remains at foundation while it has invested in AI pilots shows something that a one-time measurement cannot show: that the investment is not landing in the dimensions responsible for that. That is exactly the kind of discrepancy that executive teams often cannot resolve internally. If you want to understand why that discussion within an executive team so often gets stuck, that is worked out in why your executive team disagrees about the AI pace.
The measurement works with a plot round: several people within the organization score separately, and the spread between those scores becomes visible. That spread says something that a single average does not say. A large spread on a dimension — the CIO sees the IT infrastructure as solid, the COO sees chaos — is itself already a signal, regardless of the level the score arrives at. That spread is also a reason to repeat, but not on a fixed term. Repeat when the spread itself has become a topic of conversation, and see whether it decreases. If the spread remains large, that says something about how the organization communicates internally about AI, not about the technology itself.
The factors that can shift the score in the interim are not distributed equally across the seven dimensions. Changes in the organizational structure — a new owner for data, a different reporting line — affect the fundamental dimensions: organization, IT infrastructure, data management. If you want to know how those latter two are measured concretely, you will find that in how mature is your organization when it comes to AI and in how mature is your IT infrastructure when it comes to AI. Changes to the dependent dimensions — the dimensions that can only move once the fundamental dimensions have reached a certain level — follow this, with delay. A measurement that is repeated too early therefore often measures noise on the fundamental dimensions while the dependent dimensions could not yet move at all.
The maturity measurement cannot predict when an organization will score a level higher. It cannot indicate whether an investment in IT infrastructure will lead to a higher score within a quarter or within two years — that depends on choices the organization itself makes, on the size of the organization, and on how much internal resistance there is to change. Nor can the measurement determine whether a low score is a problem that needs to be solved, or a realistic starting point that the organization deliberately chooses. Those two scenarios for a low score are further apart than is often assumed, and are worked out in which two scenarios belong to a low score. The measurement asks questions and shows structure. It provides no timeline and no guarantee that repeating will yield a higher score.
Because the fundamental dimensions move slowly, repeating within a few months makes little sense — the time is too short to make change in organization, IT infrastructure, or data management visible. It is more meaningful to repeat at the moment there is a concrete reason: a decision about data governance, a reorganization, a major investment in AI that does or does not take hold. The measurement is then not an annual routine, but an instrument that you deploy at the moment you want to know whether a change you feel internally is also measurable in the seven dimensions.
The maturity measurement is about carrying capacity: can the organization support AI, is there enough on the fundamental dimensions to build further. It is not about which work AI can take over. If you want to know what changes in the day-to-day work itself — which part of a task, a role, or a process AI can actually take over — that is a different question, with a different instrument. The work scan of FTE TO AI calculates per task which part of the work can be taken over, regardless of whether the organization as a whole is already ready for it. These two measurements — carrying capacity and takeover potential — do not answer each other, but together they provide the complete picture with which an executive team can substantiate a decision.
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.