{"id":4214,"date":"2026-08-25T09:00:00","date_gmt":"2026-08-25T09:00:00","guid":{"rendered":"https:\/\/palegoldenrod-boar-492303.hostingersite.com\/?p=4214"},"modified":"2026-08-23T12:10:21","modified_gmt":"2026-08-23T12:10:21","slug":"ai-maturity-model","status":"publish","type":"post","link":"https:\/\/growthnation.ai\/insights\/ai-maturity-model\/","title":{"rendered":"AI Maturity Model: The 5 Stages of AI Adoption Explained"},"content":{"rendered":"Reading Time: <\/span> 11<\/span> minutes<\/span><\/span>\n

Quick Answer: <\/strong>An AI maturity model is a staged framework that rates how deeply and effectively an organisation uses AI, scored across dimensions such as strategy, data, governance, skills and measured value. Most published models use four or five stages, running from informal experimentation through to AI reshaping the operating model itself. The stage you land on matters far less than the gaps that stage number hides.<\/em><\/p>\n\n\n\n

Deloitte\u2019s State of AI in the Enterprise 2026<\/a>, a survey of 3,235 senior leaders across 24 countries, found that 42% of organisations now rate their strategy as highly prepared for AI adoption. Those same organisations rated themselves considerably less prepared on infrastructure, data, risk and talent. Deloitte describes this as being strategically ready but operationally unsure.<\/p>\n\n\n\n

That gap is the reason AI maturity models exist. It is also the reason most of them disappoint. A single overall grade averages away precisely the information a leader needs in order to act.<\/p>\n\n\n\n

This guide covers what an AI maturity model is, what each stage looks like, how the leading frameworks compare, and what actually moves an organisation up a level.<\/p>\n\n\n\n

What is an AI maturity model?<\/strong><\/h2>\n\n\n\n

An AI maturity model is a structured framework that assesses how capable an organisation is at using AI, then places it at a defined stage on a progression. It scores that capability across several dimensions rather than one, typically covering strategy, data, technology, governance, talent and business value.<\/p>\n\n\n\n

It has three practical uses: establishing a baseline, guiding investment by showing which dimension is furthest behind, and tracking movement over time so a claim of improvement can be evidenced rather than asserted.<\/p>\n\n\n\n

One distinction is worth making early, because it causes constant confusion. An AI maturity model is the framework itself. An AI maturity assessment is the exercise of scoring your organisation against one. You can run many assessments against a single model, which is rather the point of having a model.<\/p>\n\n\n\n

A credible AI maturity model looks beyond tooling. Buying more licences moves nothing on its own, because a licence is not a capability. What matters is whether the work itself has changed, which is closely tied to what agentic AI is<\/a> and how it differs from earlier automation.<\/p>\n\n\n\n

Where AI maturity models came from<\/strong><\/h2>\n\n\n\n

The five-stage shape did not originate with AI. It comes from the Capability Maturity Model, developed at Carnegie Mellon University in the late 1980s to assess how rigorously software teams followed their own processes. Its levels ran from ad hoc through to optimised.<\/p>\n\n\n\n

That structure was borrowed more or less wholesale when AI arrived. Microsoft states outright that its agentic AI adoption maturity model<\/a> is based on the Capability Maturity Model, and most vendor frameworks follow the same shape whether or not they say so.<\/p>\n\n\n\n

That lineage matters. The original model was built for slow-moving process audits, where an annual assessment was reasonable because the thing being measured moved slowly. AI capability does not, and that mismatch explains a great deal further down.<\/p>\n\n\n\n

The five stages of AI maturity<\/strong><\/h2>\n\n\n\n

Stage names differ between published frameworks, but the underlying progression is remarkably consistent. Informal use, then contained pilots, then something real in production, then spread across the organisation, then a genuinely changed operating model.<\/p>\n\n\n\n

The five stages below use our own naming. Other published frameworks label a broadly similar progression differently, and the comparison table further down sets the main ones side by side.<\/p>\n\n\n\n

Stage<\/strong><\/td>What it looks like<\/strong><\/td>Typical failure mode<\/strong><\/td>What moves you up<\/strong><\/td><\/tr><\/thead>
1. Unmapped<\/td>Informal individual tool use, no coordination, no view of which work is worth automating<\/td>Nothing compounds, the same solution is reinvented team by team<\/td>Establish what the work actually is before choosing tools<\/td><\/tr>
2. Contained<\/td>Funded pilots and executive interest, little reaching production<\/td>Pilots run indefinitely and never convert<\/td>Pick one workflow, give it an owner and a budget, ship it<\/td><\/tr>
3. Embedded<\/td>At least one workflow live with a named owner and measurement<\/td>Success stays trapped in the team that built it<\/td>A repeatable route from idea to production, plus broad enablement<\/td><\/tr>
4. Compounding<\/td>Wins spread across functions, agents owned centrally, ROI measured<\/td>Governance lags behind deployment speed<\/td>Central ownership of agents and continuous measurement<\/td><\/tr>
5. Self-improving<\/td>The operating model adapts and the score drives reinvestment<\/td>Drift between what is deployed and what is actually governed<\/td>Continuous re-scoring, with the score setting the next priority<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Stage 1: Unmapped<\/strong><\/h3>\n\n\n\n

Individuals use AI tools on their own initiative. Someone in marketing drafts copy with a chatbot, someone in operations has quietly built a forecasting spreadsheet, and none of it is coordinated, funded or visible to leadership. Almost all of it is generative rather than agentic AI<\/a>, assisting a person rather than completing work. The defining feature is not an absence of tools. It is that nobody has established which work is genuinely worth automating, so the same solution gets reinvented team by team and nothing accumulates.<\/p>\n\n\n\n

Stage 2: Contained<\/strong><\/h3>\n\n\n\n

Pilots exist, they have budget, and executives are paying attention. What they lack is reach. Results stay inside the team that ran them and little converts into production. This is where most organisations stall, and they can stall for years, because commissioning another pilot always feels like forward motion.<\/p>\n\n\n\n

Stage 3: Embedded<\/strong><\/h3>\n\n\n\n

At least one workflow genuinely runs on AI in production, with a named owner, a budget and measurement attached to it. One workflow truly in production is worth more than ten pilots that never shipped. The risk is that success stays trapped in the team that built it, which is the containment problem in a more advanced form.<\/p>\n\n\n\n

Stage 4: Compounding<\/strong><\/h3>\n\n\n\n

Wins spread across functions. Each AI agent<\/a> is owned centrally rather than living in an individual employee\u2019s personal account, so capability stays with the organisation when people leave. Returns are measured rather than argued. The usual failure at this stage is governance lagging behind deployment speed, and Deloitte found only one in five companies has a mature governance model for autonomous agents.<\/p>\n\n\n\n

Stage 5: Self-improving<\/strong><\/h3>\n\n\n\n

The operating model itself adapts. Agents run material parts of the work, the score decides where the next investment goes, and improvement becomes continuous rather than project-based. Very few organisations are genuinely at this stage.<\/p>\n\n\n\n

Most readers will place themselves at stage two or three, and the data supports that. McKinsey<\/a> found that nearly two-thirds of organisations have not yet begun scaling AI across the enterprise, and just 39% report any EBIT impact at enterprise level. Deloitte\u2019s split is similar: 34% are using AI to deeply transform, 30% are redesigning key processes around it, and 37% are using it at a surface level with little or no change to how the work is done.<\/p>\n\n\n\n

How the leading AI maturity frameworks compare<\/strong><\/h2>\n\n\n\n

Several organisations publish competing models. They differ more in vocabulary than in substance, and once you line them up the shared assumptions become difficult to miss.<\/p>\n\n\n\n

Framework<\/strong><\/td>Stages<\/strong><\/td>Stage names<\/strong><\/td>Dimensions<\/strong><\/td>Cadence<\/strong><\/td><\/tr><\/thead>
Gartner<\/td>Five<\/td>Foundational, Emerging, Operational, Scaled, Transformational<\/td>Seven pillars, including strategy, data, governance and operating model<\/td>Periodic assessment<\/td><\/tr>
Microsoft<\/td>Five<\/td>Initial, Repeatable, Defined, Capable, Efficient<\/td>Five pillars, including governance, technology and culture<\/td>Periodic assessment<\/td><\/tr>
Capability Maturity Model<\/td>Five<\/td>Initial, Repeatable, Defined, Managed, Optimising<\/td>Software process rigour, the original 1980s lineage<\/td>Periodic audit<\/td><\/tr>
GrowthNation<\/td>Score out of 100<\/td>Scored per team and organisation wide<\/td>Derived from interviews across every team, tied to hours saved<\/td>Continuous, updated as work is mapped<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

One correction is worth making, because it is widely repeated. A great many published summaries still list Gartner\u2019s stages using an earlier set of names. The current Gartner model<\/a> runs Foundational, Emerging, Operational, Scaled and Transformational, assessed across seven pillars. If you intend to benchmark against Gartner, use the version currently published.<\/p>\n\n\n\n

What these frameworks share is more revealing than what separates them. All assess multiple dimensions, all describe a progression from ad hoc to optimised, and all are scored periodically, usually by an external assessor. That last shared assumption is the one worth questioning.<\/p>\n\n\n\n

Where traditional AI maturity models fall short<\/strong><\/h2>\n\n\n\n

None of this makes the established frameworks useless. Any of them beats having no measurement at all. But three limitations surface the moment an organisation tries to act on its score.<\/p>\n\n\n\n

A single score hides the variance that matters<\/strong><\/h3>\n\n\n\n

An enterprise does not have one maturity level. Engineering might sit at stage four while finance sits at stage one, and the organisational average describes neither. This is what the Deloitte finding exposes. Rating your strategy as highly prepared while rating data, infrastructure, risk and talent as far less prepared is not a contradiction. It is what a real organisation looks like from the inside, and a single averaged grade conceals it.<\/p>\n\n\n\n

An annual grade is stale before it circulates<\/strong><\/h3>\n\n\n\n

This is the flaw inherited directly from the Capability Maturity Model lineage. Periodic assessment made sense for software process audits. Applied to a capability that shifts every quarter, an annual grade describes an organisation that no longer exists by the time anyone reads the report. It also makes progress invisible between assessments, which is precisely when budget decisions get made.<\/p>\n\n\n\n

Knowing your stage does not tell you what to do on Monday<\/strong><\/h3>\n\n\n\n

This is the largest gap. McKinsey found that fundamentally redesigning workflows has the strongest link to EBIT impact of any factor studied, yet only 21% of adopters had fundamentally redesigned any workflow at all. MIT\u2019s NANDA study reported that 95% of enterprise generative AI pilots produced no measurable return, although that figure rests on a small sample of 52 interviews and 153 survey responses and is contested on how narrowly it defines success. Sample caveats aside, the pattern is consistent. Organisations can name their stage. What they cannot name is which work to hand over first, and no stage label will tell them. AI agents for business<\/a> deliver returns when they are pointed at work that has been properly identified beforehand.<\/p>\n\n\n\n

How to measure AI maturity continuously<\/strong><\/h2>\n\n\n\n

If the limitations are cadence and granularity, the answer is not a better set of stage names. It is a different way of producing the score. Four things change when maturity is measured continuously rather than annually.<\/p>\n\n\n\n