The enterprise-AI market has converged on a single vocabulary — maturity, roadmap, workstreams, value at scale. The words are correct. They stop one floor above the thing that decides whether any of it works.
Put a dozen of the major frameworks next to each other — the analyst maturity models, the global-consultancy playbooks — and something strange happens. They stop looking like competing answers and start looking like one answer with different cover art. A maturity scale running from early experimentation to leading-at-scale. A set of dimensions or pillars to be assessed: strategy, data, governance, engineering, operating model, people and culture. A roadmap. Value at scale. Change the rung-count — five stages here, six dimensions there, seven pillars, eight dimensions, three functions — and the skeleton underneath is identical. Independent analysts have started saying it out loud: strip the branding off the frameworks and nearly every firm is selling the same handful of workstreams.
I want to be careful here, because there is a cheap version of this observation and a real one, and only the real one is worth your time.
The Words Are Not the Problem
The cheap version is to roll your eyes at the vocabulary — to call “maturity” and “roadmap” and “value at scale” buzzwords and leave it there. That is wrong, and it is lazy. The words are correct. Maturity is a real property of an organization. Roadmaps are real and necessary. Workstreams describe real work. These terms earned their place because they name things that exist. This is not a complaint about jargon, and if it were, it would be beneath the subject.
“Do you understand the graphic above? Neither do I — and neither will the executive it was built for. That is the point. This is what every maturity assessment actually looks like once you stop being impressed by it: a wall of confident readings that no one in the room can convert into a decision. The clarity isn’t missing by accident. It’s missing because the thing that would make it legible — the alignment underneath — was never on the chart.”
The real version is harder, and it is structural. The terms are right. They are also, every one of them, measuring the same axis — and it is the wrong axis.
What Every Model Measures, and What None of Them Measures
Look at what a maturity model actually does. It takes each dimension — strategy, data, governance, engineering, people — and asks how far up the scale that dimension has climbed. How advanced is your data capability. How mature is your governance. How far along is your engineering. Every pillar gets its own vertical ruler, and the assessment is a reading of how high each one reaches.
Now notice what that can never show you. Every measurement runs up and down inside a single column. Not one of them runs across. The model can tell you that your engineering is at level four and your operating model is at level two, and it will instruct you to raise the operating model — as though the problem were the height of the shorter column. But the failure was never the height of any column. It is the gap between them. It is whether your level-four engineering and your level-two operating model are aligned with each other, or are quietly working from different assumptions about timing, ownership, dependency, and sequence.
That gap has no rung. There is no dimension on the maturity model called the seam between the dimensions, because a vertical ruler cannot measure a horizontal distance. So the one place where capability actually dies — the misalignment that lives between two functions that are each, on their own, perfectly mature — is the one place the entire category of framework is built not to see.
This is why a capable system is so dangerous in these organizations. Point it at the seam between two well-developed but unaligned functions and it does not heal the seam. It executes against the misalignment at speed — faster, more confident, and no more correct than the broken handoff it inherited. High maturity on every pillar and no alignment across them is not safety. It is a well-engineered way to industrialize your own gaps.
The Tell: They Can Already See It Isn’t the Technology
Here is the part that should settle it. The firms producing these models are not fools, and many of them have looked straight at the floor without standing on it. Read the fine print and you find admissions that the thing keeping organizations from value is not the technology — it is mismatched expectations, misaligned applications, implementation that was never tested against real conditions. You find acknowledgments that the frameworks miss the granular variation, that they assess the organization in the aggregate and lose the exact place where the work breaks.
They have diagnosed the symptom of the missing floor. And then, having seen it, they prescribe more climbing — raise the lagging pillar, mature the weak dimension, advance along the roadmap. It is the oldest move in transformation, and I have watched every framework make it for thirty years: name the right variable, and then do not change the result. Seeing that it is not the technology, and then handing the client a more elaborate way to manage the technology, is naming the variable and walking past it.
What the Floor Actually Is
The floor has a name: the substrate — the layer of conditions beneath the functions that has to be aligned before any technology is pointed at them. I built a diagnostic to read it before anything ships. But the name matters less than the proof, and the proof is old.
In 1998 a Department of National Defence operation was running parts delivery at 51% against a 90% requirement. Every instinct in the room said the fix was a system. It was not. The fix was discovering that the timing of orders silently governed customs windows, courier schedules, inventory, and pricing — four functions that were each running acceptably on their own and were catastrophically unaligned with one another. No maturity model would have flagged it, because every one of those functions would have scored fine on its own column. The misalignment lived in the seams between them. Align the seams, and delivery moved to 97.3% and held there for seven years. No new technology entered the building. The conditions changed — long before the current vocabulary existed to miss them.
The substrate isn’t more tech. It is how humans and AI agents align with the tech that already exists.
Why This Is the Whole Game Now
The numbers everyone cites are real and they all point the same way: near-universal adoption, near-zero realized value. Most organizations now use AI somewhere; almost none describe their efforts as mature; a majority of senior executives report no revenue or cost benefit at all. The standard reading is that these organizations are early on the maturity curve and need to climb. The reading I would offer is that they climbed exactly as instructed — raised every pillar, followed the roadmap — and hit the gap the roadmap doesn’t contain.
The convergence on the vocabulary is not a problem to resent. If anything, it is the market building the on-ramp — teaching an entire generation of leaders to expect the wall. They have the right words for it now. What they do not yet have is the floor underneath the words.
The whole field agreed on what to call the climb. The work left is the work it skips: identify the seams, and find the floor.
-30-
Truth Is Believing. Accuracy Is Knowing.
Jon Hansen is the creator of Implementation Physics™, a research-based framework developed over nearly three decades to explain why technology initiatives succeed or fail. Supported in part through Canada’s Scientific Research & Experimental Development (SR&ED) program, his work spans six technology generations—from ERP through Agentic AI—and examines the organizational conditions that determine outcomes regardless of the technology being deployed.
His research forms the foundation for the Hansen Method™, Hansen Fit Score™ (HFS), Phase 0™ Readiness Assessment, and ARA™/RAM 2025™ multimodel verification architecture.
Hansen currently serves as a Board Member of the CIPS Americas Chapter.
Related
Everyone Found the Right Words. No One Reached the Floor.
Posted on June 12, 2026
0
The enterprise-AI market has converged on a single vocabulary — maturity, roadmap, workstreams, value at scale. The words are correct. They stop one floor above the thing that decides whether any of it works.
Put a dozen of the major frameworks next to each other — the analyst maturity models, the global-consultancy playbooks — and something strange happens. They stop looking like competing answers and start looking like one answer with different cover art. A maturity scale running from early experimentation to leading-at-scale. A set of dimensions or pillars to be assessed: strategy, data, governance, engineering, operating model, people and culture. A roadmap. Value at scale. Change the rung-count — five stages here, six dimensions there, seven pillars, eight dimensions, three functions — and the skeleton underneath is identical. Independent analysts have started saying it out loud: strip the branding off the frameworks and nearly every firm is selling the same handful of workstreams.
I want to be careful here, because there is a cheap version of this observation and a real one, and only the real one is worth your time.
The Words Are Not the Problem
The cheap version is to roll your eyes at the vocabulary — to call “maturity” and “roadmap” and “value at scale” buzzwords and leave it there. That is wrong, and it is lazy. The words are correct. Maturity is a real property of an organization. Roadmaps are real and necessary. Workstreams describe real work. These terms earned their place because they name things that exist. This is not a complaint about jargon, and if it were, it would be beneath the subject.
“Do you understand the graphic above? Neither do I — and neither will the executive it was built for. That is the point. This is what every maturity assessment actually looks like once you stop being impressed by it: a wall of confident readings that no one in the room can convert into a decision. The clarity isn’t missing by accident. It’s missing because the thing that would make it legible — the alignment underneath — was never on the chart.”
The real version is harder, and it is structural. The terms are right. They are also, every one of them, measuring the same axis — and it is the wrong axis.
What Every Model Measures, and What None of Them Measures
Look at what a maturity model actually does. It takes each dimension — strategy, data, governance, engineering, people — and asks how far up the scale that dimension has climbed. How advanced is your data capability. How mature is your governance. How far along is your engineering. Every pillar gets its own vertical ruler, and the assessment is a reading of how high each one reaches.
Now notice what that can never show you. Every measurement runs up and down inside a single column. Not one of them runs across. The model can tell you that your engineering is at level four and your operating model is at level two, and it will instruct you to raise the operating model — as though the problem were the height of the shorter column. But the failure was never the height of any column. It is the gap between them. It is whether your level-four engineering and your level-two operating model are aligned with each other, or are quietly working from different assumptions about timing, ownership, dependency, and sequence.
That gap has no rung. There is no dimension on the maturity model called the seam between the dimensions, because a vertical ruler cannot measure a horizontal distance. So the one place where capability actually dies — the misalignment that lives between two functions that are each, on their own, perfectly mature — is the one place the entire category of framework is built not to see.
This is why a capable system is so dangerous in these organizations. Point it at the seam between two well-developed but unaligned functions and it does not heal the seam. It executes against the misalignment at speed — faster, more confident, and no more correct than the broken handoff it inherited. High maturity on every pillar and no alignment across them is not safety. It is a well-engineered way to industrialize your own gaps.
The Tell: They Can Already See It Isn’t the Technology
Here is the part that should settle it. The firms producing these models are not fools, and many of them have looked straight at the floor without standing on it. Read the fine print and you find admissions that the thing keeping organizations from value is not the technology — it is mismatched expectations, misaligned applications, implementation that was never tested against real conditions. You find acknowledgments that the frameworks miss the granular variation, that they assess the organization in the aggregate and lose the exact place where the work breaks.
They have diagnosed the symptom of the missing floor. And then, having seen it, they prescribe more climbing — raise the lagging pillar, mature the weak dimension, advance along the roadmap. It is the oldest move in transformation, and I have watched every framework make it for thirty years: name the right variable, and then do not change the result. Seeing that it is not the technology, and then handing the client a more elaborate way to manage the technology, is naming the variable and walking past it.
What the Floor Actually Is
The floor has a name: the substrate — the layer of conditions beneath the functions that has to be aligned before any technology is pointed at them. I built a diagnostic to read it before anything ships. But the name matters less than the proof, and the proof is old.
In 1998 a Department of National Defence operation was running parts delivery at 51% against a 90% requirement. Every instinct in the room said the fix was a system. It was not. The fix was discovering that the timing of orders silently governed customs windows, courier schedules, inventory, and pricing — four functions that were each running acceptably on their own and were catastrophically unaligned with one another. No maturity model would have flagged it, because every one of those functions would have scored fine on its own column. The misalignment lived in the seams between them. Align the seams, and delivery moved to 97.3% and held there for seven years. No new technology entered the building. The conditions changed — long before the current vocabulary existed to miss them.
The substrate isn’t more tech. It is how humans and AI agents align with the tech that already exists.
Why This Is the Whole Game Now
The numbers everyone cites are real and they all point the same way: near-universal adoption, near-zero realized value. Most organizations now use AI somewhere; almost none describe their efforts as mature; a majority of senior executives report no revenue or cost benefit at all. The standard reading is that these organizations are early on the maturity curve and need to climb. The reading I would offer is that they climbed exactly as instructed — raised every pillar, followed the roadmap — and hit the gap the roadmap doesn’t contain.
The convergence on the vocabulary is not a problem to resent. If anything, it is the market building the on-ramp — teaching an entire generation of leaders to expect the wall. They have the right words for it now. What they do not yet have is the floor underneath the words.
The whole field agreed on what to call the climb. The work left is the work it skips: identify the seams, and find the floor.
-30-
Truth Is Believing. Accuracy Is Knowing.
Jon Hansen is the creator of Implementation Physics™, a research-based framework developed over nearly three decades to explain why technology initiatives succeed or fail. Supported in part through Canada’s Scientific Research & Experimental Development (SR&ED) program, his work spans six technology generations—from ERP through Agentic AI—and examines the organizational conditions that determine outcomes regardless of the technology being deployed.
His research forms the foundation for the Hansen Method™, Hansen Fit Score™ (HFS), Phase 0™ Readiness Assessment, and ARA™/RAM 2025™ multimodel verification architecture.
Hansen currently serves as a Board Member of the CIPS Americas Chapter.
Share this:
Like this:
Related