Maturity Assessment
A demo that gets applause and then falls flat is not an accident. It is the result of a structure that does not move along with the technology. The maturity assessment makes visible where that structure stands. What you do next with that outcome is a choice between three routes. This page describes them in the order that fits what the tool is: first yourself, then partly guided, only then outsourced.
The order is not arbitrary. A route that starts with outsourcing is really selling an advisory trajectory with an assessment glued on the front. That is not what happens here. The tool remains the record in all three routes: the place where scores, scenarios and decisions are captured, even when you bring in a partner.
What you get: a route map per dimension, built according to the fundamentals-first rule, with pilot rules that establish in advance what a pilot must prove, what happens if it does not, and what is needed to scale up. No more loose experiment, but a sequence with a decision framework attached.
This route fits when the organisation already has some form of project-based management, when there is someone who can hold the approach sequence together across multiple departments, and when the board and management are already somewhat aligned on pace. The tool structures the conversation; it does not conduct it for you.
What it asks: your own capacity to guard the pilot rules, someone who dares to stop when a pilot does not meet the condition set in advance, and the discipline not to skip the fundamental dimensions because the visible one — the chat window — seems to deliver results faster.
This route does not fit when the operating model itself is up for debate: if roles, decision rights or governance need to be redesigned, that is a design question the tool does not solve. See also what it is for the precise scope of the assessment itself.
What you get: the same assessment, the same record, supplemented by a partner who redesigns the operating model with you and shapes the governance setup — a decision inventory and agent rules as a starting point, worked out in consultation. The assessment stays in the tool; the design work shifts to people.
This route fits when the score on one or more dimensions is low enough that doing it yourself is not realistic, or when the board and management do have a shared picture of execution capacity but not of how the structure needs to change. Also when workforce planning and AI strategy keep getting stuck in separate meetings, a partner can bring those two lines together.
What it asks: willingness to hand over part of the design, and someone internally who translates the outcomes of that design back to your own organisation. The tool supplies the record; the partner works with it, not in your place.
This route does not fit when the organisation really only needs execution — then partly guided is an intermediate step that adds nothing. And it does not fit when there is not yet any shared picture at all of where the organisation stands; that picture only emerges through the plot round described in how it works, not through a partner starting without that foundation.
What you get: a full human+machine trajectory at the partner, with the assessment serving as the baseline measurement. The tool records where you start; the partner carries out the trajectory that follows.
This route fits when urgency is high, internal capacity for both design and execution is lacking, or when the board wants an external party to carry the execution while the organisation itself continues day-to-day business. Also when earlier pilots have stalled without it being clear why, a baseline measurement can restore the starting point.
What it asks: a clear brief in advance, and the willingness to leave the trajectory with a partner without the organisation continually steering along. Outsourcing does not work if everyone still wants to stay at the wheel themselves.
This route does not fit when the organisation itself already has sufficient structure and capacity — then outsourcing is a more expensive version of what route 1 can already do. And it does not fit as a substitute for the assessment itself: there are no completed trajectories to point to, and the tool makes no promise about what a trajectory will deliver. It structures the starting point; the outcome depends on what happens afterwards.
In all three cases the assessment itself remains unchanged: the same plot round, the same scores, the same record. The difference lies in who does the design and execution that follow the report. More on the background to these choices — operating model, decision-making, pace — can be found in the knowledge base.
Whatever route fits: the score says something about readiness, not about the concrete load AI is going to place on the organisation. That only becomes clear in tasks, hours and systems — the subject of the work scan at ftetoai.com.
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.