Every single enterprise AI maturity assessment I've seen shares the same five axes:
- Seats licensed,
- prompts per week
- Percentage of teams onboarded
- Executive sentiment
- A number somebody on the slide calls "adoption velocity."
Score high on all five and the "model" declares that you are advanced. Score low and you get a roadmap with more seats on it, brought to you by a model provider looking to sell more seats/tokens/licenses.
Not one of those axes asks whether the work is correct.
That omission isn't an oversight, it's the whole point of the model. A company can land in the top 10% for AI spending and the bottom 10% for AI maturity in the same fiscal year, and the adoption dashboard won't tell you which one you're looking at, because it was never built to ask the right question. Meanwhile the review queue is drowning, defect escape rates are climbing, and every chart on the transformation deck is green.
What CMMI got right that this generation forgot# #
Software has graded organizational maturity before, and it did a better job of it than the current crop of AI radar charts.
The Capability Maturity Model, and later CMMI, spent the 1990s and 2000s scoring software organizations on a five-level scale. You had to produce artifacts, document processes, and provide historical defect data, not just an opinion or vibes.
Whether those artifacts reflected real behavior or became a target unto themselves is CMMI's own well-known second problem: appraisers were typically engaged and paid by the organization being assessed, and level-shopping became a real, documented criticism of the standard. But it set a floor that current AI maturity models don't even try to clear: an opinion is not evidence.
Today's AI maturity models threw that decision away. They ask a director to rate their organization's "AI readiness" on a scale of one to five and call the average an assessment. That is not a maturity model. That is a satisfaction survey wearing a rubric as a costume, and satisfaction surveys become gamified the moment they matter to anyone's bonus.
Maturity is where trust lives# #
This Agentic Maturity Model is built on and around this core principle: maturity is not how much AI a company produces. It is what mechanism establishes that the work is correct, and whether that mechanism scales.
Everything else you would normally put on a maturity radar (tooling, knowledge architecture, observability, unit economics) is downstream of that one, key principle. It matures as a consequence of trust moving from human attention to a verified, compounding system. It does not mature on its own, no matter how many licenses you buy.
I call that principle "trust location". It is the actual axis of evaluation. Seats and tokens are a shadow it casts on the wall, a subsequent effect, and most enterprise AI strategy is currently spent measuring the shadow.
Three rules for a model that can't be gamed# #
A maturity model that can be improved by enthusiasm will be improved by enthusiasm, and nothing else. So this one is built to three constraints, inherited from a lifecycle argument I made in the description of an Agentic Development Lifecycle and worth restating here because they are the whole reason this model is worth trusting:
Audit-checkable, not sentiment-checkable. Every level is defined by a structural fact you could verify in an afternoon: a log, an artifact, a query against production data. Not a survey answer. If the only evidence for your level is a director's confidence, you don't have a level yet.Transitions are driven by pain, not aspiration. Nobody climbs a level because a slide said to. Each level ends because its trust mechanism hits a wall it cannot get past, and the organization is forced up or it stalls. Find the pain, and you've found the level.Maturity is not monotone in AI usage. A team running four copilots and a chatbot can burn more tokens in a week than a team running a disciplined agent pipeline burns in a month, and the second team is the mature one. Mature organizations spend deliberately, concentrated where an error is expensive to catch late. They do not spend everywhere enthusiasm reaches.
That third rule is the one that breaks the adoption-curve story completely, because it means the leaderboard your vendor sends you every quarter, ranked by spend, is not just incomplete. It can be inverted. The company at the top of that leaderboard may be the one paying the most to generate the least trustworthy output at scale.
I wrote a series on the Agentic Development Lifecycle for the practitioner who has to actually build a system where the work is verified rather than merely produced. This series is for the person who signs off on that practitioner's budget, and who is currently being told by every dashboard in the building that Level 2 is the destination.
It isn't. The next two posts build the rest of the map. The five levels name where trust actually sits today, wall by wall. The diagonal law explains why almost every AI failure your board hears about, and a few that haven't reached the board yet, are the same misalignment wearing a different name.
Find your organization on the adoption curve if you want. It will tell you how much you spent. It will not tell you what you bought.