--- title: Quotient AI Adoption Maturity Model synced_from_vault: true vault_source: 03-living-docs/patterns/Quotient-AI-Maturity-Model.md public: true name: Quotient AI Adoption Maturity Model description: >- Org-level maturity framework for engineering AI adoption. Five stages across six capability dimensions. Use to self-assess where the team is and what has to change to move up a stage. type: pattern category: change-management tags: - pattern - change-management - ai-adoption - framework - engineering origin: 'Quotient (engineering AI platform) — summarized in Lizzie Matusov''s [RDEL' --- > **Core concept:** Engineering AI adoption doesn't mature by tool usage alone — it matures through organizational capability. Five stages of practice, assessed across six capability dimensions. Being "at a stage" means hitting the bar on enough dimensions, not owning a tool. --- ## The Framework ### Five Stages | Stage | Character | What it looks like | |-------|-----------|--------------------| | **1 — Ad Hoc Experimentation** | Individual tinkering | Developers try AI tools on their own. No policy, no infrastructure, no org-level expectations. The fastest people are far ahead of the rest; most of the team is still curious or skeptical. | | **2 — Coordinated Experimentation** | Shared learning | Teams are starting to share what works. Informal norms emerge. Some training, maybe a Slack channel, maybe a show-and-tell. Still no formal policy or validation — but the practice is no longer purely individual. | | **3 — Embedded Workflows** | Routine integration | AI is embedded in engineering workflows. Formal training exists. Usage policies are written and followed. Validation checks are automated. AI has access to internal documentation. This is the first stage that's auditable. | | **4 — Guided Automation** | Task-level autonomy | AI automates well-defined tasks end-to-end (e.g., test generation, doc updates, simple refactors). Engineers retain oversight of higher-risk decisions. Workflow automation is real but bounded. | | **5 — Autonomous Workflows** | Multi-step orchestration | AI orchestrates multi-step engineering workflows across systems with minimal human intervention. Humans set direction and review outcomes, not every step. | > **Stage-name caveat:** Quotient (via RDEL) uses numbered stages with descriptions; the descriptive names above are our synthesis of the descriptions. Reference the numbers in external communication if precision matters. ### Six Capability Dimensions Each stage is defined by the org's maturity across six capability areas. You can be strong in one dimension and weak in another — the **stage is set by the weakest dimension that gates the next tier.** | # | Dimension | What it measures | |---|-----------|------------------| | 1 | **Enablement** | Training, tools, licenses, skills distribution across the team. Are engineers equipped to use AI effectively? | | 2 | **Policy and Governance** | Formal AI policy, acceptable-use rules, accountability for AI-assisted decisions. Does the org have a documented posture? | | 3 | **Validation and Testing** | Automated checks on AI output. Does the AI's work get reviewed, measured, and validated systematically? | | 4 | **Workflow Embedding** | AI integrated into the day-to-day engineering flow — PRs, reviews, docs, planning. Is AI part of how work actually gets done, or is it adjacent? | | 5 | **Workflow Automation** | Tasks AI handles end-to-end without per-step human action. What's the autonomy surface? | | 6 | **Data Context and Access** | AI has structured access to internal documentation, codebases, context. Can AI work with the organization's actual information, or only public data? | --- ## Why This Framework - **Ties tool usage to practice maturity.** A team with lots of Claude seats but no validation, no policy, and no embedding is Stage 1 — not Stage 3. Prevents optics-over-substance self-assessment. - **Makes gaps concrete.** "Where are we" becomes "which of the six dimensions is weakest?" — an answerable question with a prescribed remediation. - **Aligns to audit frameworks.** ISO/IEC 42001 audits against real practice (policy, impact assessment, lifecycle, data governance). Quotient's six dimensions map onto those audit concerns almost directly. A Stage 3+ org is plausibly ISO 42001 certifiable; a Stage 1–2 org is not. - **Prescribes the next move.** The biggest leverage gain is usually getting from Stage 1 (individual tinkering) to Stage 2–3 (coordinated, embedded) — *not* chasing Stage 5 prematurely. Stage 3 is the right target for most orgs. --- ## How to Use It **For self-assessment:** 1. Score the org 1–5 on each of the six dimensions. 2. The overall stage = the lowest score that blocks the next tier. (An org with Enablement=3 but Policy=1 is at Stage 1 — policy is the gate.) 3. Identify the weakest dimension. That's the next-quarter's focus. **For sequencing initiatives:** - ISO 42001 certification requires being at Stage 3 across most dimensions. Don't schedule certification work before the practice exists. - Workflow automation (Dimension 5) presumes workflow embedding (Dimension 4) is already solid. Don't automate what you haven't embedded. - Training (Dimension 1) without policy (Dimension 2) creates uneven adoption — individuals go fast, org stays disorganized. **For 1:1s and coaching:** - Individual maturity (e.g., STRV's 6-level per-engineer framework) feeds Dimension 1 (Enablement). It does not substitute for the org score. - The AI Adoption Tracker's Knoster assessment diagnoses *why* individuals are where they are — which is a coaching tool, not a stage measure. --- ## Key Distinction — Individual vs. Org | Signal | What it tells you | What it doesn't tell you | |--------|-------------------|--------------------------| | Individual Claude usage | Personal capability; enablement distribution | Whether the team has a shared practice | | Show-and-tell attendance | Curiosity signal | Whether anything changed after | | A few Level-5 engineers | There's capability ceiling in the room | Whether workflow embedding or policy exists | | "We use AI every day" | Informal adoption is happening | Whether validation, governance, or auditability exist | **Individual capability distribution is one input to Dimension 1 (Enablement). It is NOT the org stage.** --- ## Cross-References - [Augmentation-Over-Automation](/patterns/augmentation-over-automation) — design philosophy underpinning what "embedded workflows" should actually look like - [You-Cant-Skip-Phases](/patterns/you-cant-skip-phases) — Greiner's growth-phases lens; Quotient is a phased maturity model in the same family — can't skip stages - [Effectiveness-Over-Efficiency](/patterns/effectiveness-over-efficiency) — informs what Stage 4/5 automation should target (do the right things, not just do things faster) ## Source - [RDEL #136: How can engineering leaders assess their AI maturity? (Lizzie Matusov, Substack)](https://rdel.substack.com/p/rdel-136-how-can-engineering-leaders) — summary of the Quotient framework used in this pattern