A management team states an ambition: AI takes over part of the work, people spend their time on something else. The sentence sounds simple. What lies behind it is not. Ambition is a statement about the future. Capability is a statement about what the organization can do today. Between the two lies a difference that is rarely named, and that is precisely where most efforts stall. Not because the ambition is wrong, but because no one has established what needs to be in place before the ambition is anything more than a wish.
The ambition assessment therefore records ambitions in four layers: the vision, the vision state that goes with it, the target, and the target state that makes concrete when the target has been reached. Those four layers are tested for readiness across eight dimensions, with five confidence gates that indicate how certain an outcome is. At the end follows a capability translation: which roles and decision rights are needed to actually carry the ambition. That is a different conversation from the conversation about the ambition itself, and it is precisely the conversation that is usually skipped.
AI takes over work. Not as a prediction, but as something that is already happening in parts today. Three categories run through every work process: tasks AI can already take over, tasks that are partly taken over with human oversight that approves or rejects with reason, and tasks that remain human work. At one company that division has already been clearly mapped out and the organization works with it. At another company the ambition exists only on paper, while no one can say which tasks fall into which category.
That difference does not come from chance. It comes from readiness. An organization that knows which decisions require oversight and who may provide that oversight can shift work as soon as the technology allows it. An organization that does not know this remains stuck at the ambition, even when the technology is already available. What is the difference between being ready and being enthusiastic shows where that difference comes from and why enthusiasm is not a predictor of execution.
The ambition assessment is an estimate, not a retrospective measurement. That deserves to be stated, also on this page. A confidence gate indicates how certain an outcome is, not that the outcome is true. For a dimension where little information is available, the outcome remains uncertain, and that is shown rather than hidden. A low confidence on a dimension does not mean the organization is not ready; it means too little is known to say anything about it. That is a different signal, and it calls for a different follow-up: first gather more information, not immediately adjust course.
There is also a limit to what the assessment can say about sequence. When multiple dimensions lag behind at the same time, the question is not which dimension scores worst, but which dependencies determine what needs to happen first. Which order should you follow when three dimensions lag behind at the same time goes further into this, because a score without sequencing logic yields little.
And the assessment says nothing about whether a measure taken earlier has actually landed. A readiness score that improved three months ago may have slipped back in the meantime without anyone noticing, unless it is measured again. How do you measure whether an improvement has truly landed describes why a one-time measurement is never the whole story.
There are situations in which the ambition assessment does not provide a meaningful answer. If the four layers of the ambition are not consistent — if the vision promises something different from what the target state makes concrete — then the method tests a contradiction, and the outcome reflects that contradiction rather than the actual readiness. If a management team interprets the eight dimensions differently, a score emerges that is not internally comparable. The assessment presupposes a certain degree of shared understanding beforehand; without that understanding it mainly measures confusion. How do I get my management team aligned discusses what is needed for that before an assessment yields anything.
The capability translation has a similar limit. Roles and decision rights that are correct on paper say nothing about whether they also function that way in practice. That only becomes apparent once the work actually shifts, not when the scheme is approved.
The outcomes of the ambition assessment say something about the readiness of work processes and decision structures, not about individual employees. Where an outcome touches on personnel decisions, separate legal requirements apply; these are not addressed here and the assessment is not designed to substantiate them. The assessment also does not guarantee that a task will actually be taken over by AI: that depends on technology, on oversight, on what the organization actually puts in place. The underlying question — which work in this company can genuinely be taken over by AI — is answered per task with the work scan from FTE TO AI, separate from the ambition assessment itself.
Anyone who wants to know where their own organization stands does not start with the full assessment, which is still under construction. There is a free readiness check: eight short questions, one per dimension, that give a picture of where the organization is furthest along and where it lags the most. That picture is an initial indication, not a final verdict, and precisely for that reason a suitable starting point for the conversation that otherwise would not take place. Anyone who first wants to know how recognizable it is that an ambition is overtaxing the organization will find pointers to that in how do you recognize an ambition your organization cannot handle.
Vertel wat u wilt bereiken, dan kijken we samen wat daarvoor moet staan.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.