A CHRO who looks at AI maturity does not look first at systems. That person looks at people, roles, and the question of whether the organization can carry a change of this magnitude without breaking. That is a different angle than that of a CIO or a CEO, and that is precisely why this role needs its own answer.
When AI pilots stall, the CHRO sooner or later gets the bill for it. Unrest on the work floor, resistance from teams who don't know what is expected of them, managers deploying AI without consulting HR, and an organization growing change-fatigued before anything structural has been put in place. The CHRO loses the most here when the organization treats AI as an IT project instead of a change that cuts through the entire workforce structure.
What a CHRO wants to gain is something else: an organization that knows who is responsible for what once AI takes on a role in the work, roles that have been redescribed rather than silently changed, and a change process that takes people along instead of catching them off guard. That gain does not start with an AI tool. It starts with the question of whether the organization itself is ready.
The question a CHRO asks is not "which tasks will disappear". That question comes later, and belongs to a different instrument. The question that must be asked first is: is the organization positioned in such a way that a change like AI lands responsibly? Are roles, responsibilities, and decision-making arranged so that people know what is being asked of them? Is there a foundation of organization, infrastructure, and data management that can carry this change, or does that change rest on a foundation that is not yet in place?
That is why the maturity assessment begins with the fundamental dimensions and not with the dependent ones. An organization cannot handle AI maturely at the level of insight or intelligence if the foundation of organization and data is still at baseline or foundation level. That order is not a choice made by the CHRO; it is the order in which it works.
A CHRO does not accept an answer based on a single impression. "It feels like we're ready for it" is not an answer on which a change process of this magnitude can be built. What does count is a picture built from multiple perspectives: how does the executive board view the organization, how does IT view it, how does a team leader on the work floor view it. If those three pictures diverge widely, that is itself information. It says something about where the organization lacks clarity, and making that spread visible is at least as valuable as the level at which the organization scores exactly.
That is why the assessment works with a plotting round in which several people score separately, without influencing each other. Not to calculate an average, but to see where the organization agrees and where it does not. For a CHRO, that is often the most useful result: not the score, but the conversation that follows the difference between what the executive board thinks and what the work floor experiences.
A CIO asks a different question, focused on infrastructure and data architecture, as described in what a CIO looks for in AI maturity. A CEO looks more broadly at the organization as a whole, which you can read about in what a CEO looks for in AI maturity. And whoever is responsible for how the work itself is organized will find an additional perspective in what a workforce leader looks for in AI maturity. These roles look at the same organization, but do not ask the same question, and that is precisely why the assessment is built per dimension and not per function.
The maturity assessment is currently being developed. There is no instrument yet that you can fill in today, and nothing is being offered here that does not yet exist. Anyone who wants to follow the development or wants to be among the first to measure how the organization stands can join the waiting list.
This assessment answers the question of whether the organization can carry AI: whether the foundations of organization, infrastructure, and data are in order before AI takes on a role in the work. That is a different question than which part of the work itself is suitable for AI to take over. That second question is answered by FTE TO AI's work scan, which calculates per task which part is suitable for AI to take over. A CHRO who has established whether the organization is ready has, with that work scan, the instrument to see where the change subsequently 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.