Maturity Matrix
Matrix/Organization

Organization

How organizations adapt to the age of agents. From "buy licenses" to "agent fleet management".

4capabilities20levels61practices61guides
The matrix · at a glance
Capability ↓
Maturity →
L1 · Stage 01
Ad-hoc
L2 · Stage 02
Guided
L3 · Stage 03
Systematic
L4 · Stage 04
Optimized
Sweet spot
L5 · Stage 05
Autonomous
01
AI Adoption Model
02
Knowledge Management
03
Team Structure & Roles
04
Tech Debt & Modernization
Capability 01 · Organization

AI Adoption Model

How your organization rolls out AI tools - from individual experiments to org-wide strategy.

L2 · Stage 02Guided
Practices - what it looks like3 guides
Criteria - what to measure
  1. 012-3 pilot teams are designated with explicit AI adoption goals
  2. 02An internal champion (or AI lead) is identified and has allocated time for the role
  3. 03Pilot metrics are defined and tracked (adoption rate, usage frequency, developer satisfaction)
  4. 04Pilot results are shared with the broader organization
  5. 05Champion has direct access to leadership for escalation
L3 · Stage 03Systematic
Practices - what it looks like3 guides
Criteria - what to measure
  1. 01Platform team formally owns AI tooling (selection, provisioning, security, baseline configuration)
  2. 02Internal Developer Platform includes an AI layer (standardized agent setup, self-service provisioning)
  3. 03Standardized agent setup exists per team (every team has a working AI environment by default)
  4. 04New developer onboarding includes AI tool setup that completes in under 30 minutes
  5. 05Platform team tracks adoption breadth (% of developers with active AI setup)
L4 · Stage 04OptimizedMost teams aim here
Practices - what it looks like3 guides
Criteria - what to measure
  1. 01AI-first development culture: 80%+ of developers use AI tools daily
  2. 02Agent fleet management is a recognized discipline with defined practices
  3. 03Developer role has shifted toward agent supervision (Yegge Stage 6-7)
  4. 04"Span of control" metric is tracked (how many agents a developer can effectively supervise)
  5. 05Organization benchmarks against industry AI adoption data (Zapier 97%, Cursor 3 adoption rates)
L5 · Stage 05Autonomous
Practices - what it looks like3 guides
Criteria - what to measure
  1. 01Centralized agent orchestration system exists ("Kubernetes for agents")
  2. 02Developer role is "human-at-the-wheel" (strategic direction, not task-level involvement)
  3. 03Organization is optimized for agent throughput, not human throughput (meetings, processes, tooling all agent-aware)
  4. 04Agent orchestration system handles scheduling, resource allocation, and failure recovery
  5. 05Organization measures agent utilization as a key infrastructure metric
Capability 02 · Organization

Knowledge Management

How institutional knowledge is captured, shared, and made available to both humans and agents.

L2 · Stage 02Guided
Practices - what it looks like3 guides
Criteria - what to measure
  1. 01Documentation refresh initiative is active with measurable progress
  2. 02Architecture Decision Records (ADRs) are written for significant technical decisions
  3. 03Written onboarding path exists (new developer can self-serve key setup steps)
  4. 04ADRs are indexed and searchable
  5. 05Onboarding path has been validated by at least one new hire completing it solo
L3 · Stage 03Systematic
Practices - what it looks like3 guides
Criteria - what to measure
  1. 01Documentation is treated as infrastructure (owned by engineering, not HR or PMO)
  2. 02Lint rules enforce conventions rather than relying on documentation alone (enforced > suggested)
  3. 03Knowledge graph of the codebase (CodeTale, Graph Buddy, or equivalent) is operational
  4. 04Documentation freshness is tracked (pages older than 90 days are flagged for review)
  5. 05Knowledge graph is integrated with agent context pipeline (agents query it at runtime)
L4 · Stage 04OptimizedMost teams aim here
Practices - what it looks like3 guides
Criteria - what to measure
  1. 01Context Fabric: MCP servers automatically feed institutional knowledge to agents
  2. 02Autonomous Requirements pipeline: unclear tickets are auto-expanded into specs with acceptance criteria
  3. 03Agents auto-update documentation when code changes (no manual doc maintenance)
  4. 04Context Fabric covers 80%+ of active repositories
  5. 05Doc auto-update PRs are reviewed and merged within 24 hours
L5 · Stage 05Autonomous
Practices - what it looks like3 guides
Criteria - what to measure
  1. 01Knowledge base is self-evolving (agents add, update, and validate knowledge entries continuously)
  2. 02Agent detects stale context, updates it, and validates the update - without human initiation
  3. 03Organizational memory is Git-backed, agent-readable, and provably current
  4. 04Knowledge base freshness score exceeds 95% (% of entries updated within their defined freshness window)
  5. 05Self-evolving updates are validated against codebase to prevent knowledge drift
Capability 03 · Organization

Team Structure & Roles

How teams are organized and what roles exist to support AI-augmented engineering.

L2 · Stage 02Guided
Practices - what it looks like3 guides
Criteria - what to measure
  1. 01AI champion is designated per team with allocated time (not just informal interest)
  2. 02Context engineer role exists (initial, possibly part-time) for maintaining agent instruction files
  3. 03Developer training on effective agent interaction (prompt writing, task decomposition) has been conducted
  4. 04Champion has a regular cadence for sharing learnings across the team
  5. 05Training materials are documented and available for new hires
L3 · Stage 03Systematic
Practices - what it looks like3 guides
Criteria - what to measure
  1. 01Platform Engineer role with AI tooling responsibility exists on the platform team
  2. 02Context Engineer is a full dedicated role (not part-time, not combined with other duties)
  3. 03Team's primary activity has shifted from writing code to evaluating and reviewing AI-generated code
  4. 04Role definitions are updated to reflect AI-augmented responsibilities
  5. 05Hiring criteria include AI tool proficiency
L5 · Stage 05Autonomous
Practices - what it looks like3 guides
Criteria - what to measure
  1. 01Agentic Engineer role combines orchestration, supervision, and architecture responsibilities
  2. 02PEV (Plan, Execute, Verify) loop is the standard workflow for all engineering tasks
  3. 03Non-coder contributors can produce software changes via agent interfaces
  4. 04Agentic Engineer career ladder exists with defined progression criteria
  5. 05Non-coder contribution rate is tracked as an organizational capability metric
Capability 04 · Organization

Tech Debt & Modernization

How AI accelerates paying down tech debt and modernizing legacy systems.

L3 · Stage 03Systematic
Practices - what it looks like3 guides
Criteria - what to measure
  1. 01Continuous modernization: agents work on tech debt reduction in background (non-blocking to feature work)
  2. 02Library version bumps and dependency upgrades are automated via agent PRs
  3. 03OpenRewrite + agent combination is used for systematic refactoring campaigns
  4. 04Agent tech debt PRs follow the same review process as feature PRs
  5. 05Dependency freshness score is tracked (% of dependencies within N versions of latest)
L4 · Stage 04OptimizedMost teams aim here
Practices - what it looks like3 guides
Criteria - what to measure
  1. 01Projects previously deemed "too expensive to modernize" are being modernized by agents at low cost
  2. 02Cross-repository migration agents operate across multiple codebases simultaneously
  3. 03Major version migrations (e.g., Java 8 to 21, Angular.js to Angular 17) are agent-driven
  4. 04Cost-per-migration-PR is tracked and decreasing
  5. 05Cross-repo migrations complete within defined SLAs (e.g., 100 repos migrated in 30 days)
L5 · Stage 05Autonomous
Practices - what it looks like3 guides
Criteria - what to measure
  1. 01Tech debt is at near-zero steady state (new debt is paid down within the same sprint it is created)
  2. 02Agent fleet maintains, upgrades, and patches codebases 24/7 without human scheduling
  3. 03CVE remediation is autonomous: detect vulnerability, generate fix, test, and ship
  4. 04Mean time from CVE disclosure to deployed fix is under 24 hours for critical vulnerabilities
  5. 05Tech debt score (measured by static analysis) has been stable or improving for 6+ months
Climb the matrix

You don't have to figure this out alone.

Every level in this matrix has a path. Read the playbooks the teams that have climbed it wrote. Run the assessment with our consultants. Start where you are.

guide12 min read↗
AI fluency curriculum for engineers
From first Copilot to autonomous agent orchestration.
playbook18 min read↗
Hiring for AI-native teams
What to look for when everyone claims AI proficiency.
workshopFull day↗
AI adoption model workshop
Map your organisation against the five maturity levels.
Live with Visdom

Book an AI Maturity Assessment session with your team.

We walk you through all four perspectives, score where you actually are, and leave you with a 90-day plan to climb in the dimensions that matter most.

Book an assessment →See what's included90-day plan - scored assessment - coaching
Author Commentary

May 2026 update: the Q1 layoff data is now in and it is uglier than the press release tour suggested.

78,557 tech jobs lost in Q1 2026, 47.9% AI-attributed, with junior and entry-level roles disproportionately affected (new SWE postings down 15%). 55% of employers report regretting AI-driven layoffs - the "AI layoff trap" is being quietly reversed. Forrester finds only 16% of workers have high AI readiness, projected to 25% by year-end. The lesson: cutting humans before maturing the AI stack creates a permanent capability gap.

Healthy adoption now includes a "bad day protocol" - a documented rollback when the model or harness regresses (the template here is Anthropic's April 23 postmortem; the diagnostic is Stella Laurenzo's 6,852-session audit). On the org side, the most interesting new pattern is IPETs (Innovation and Practices Enabling Teams) - a Team Topologies adaptation where a small enabling team owns AI stewardship, knowledge diffusion and security boundaries across product teams. New tech debt categories matter too: "context debt" (rapid iteration without architectural integrity, hits a 12-week unmaintainability cliff) and "verification debt" (3x velocity gain offset by 125% verification overhead). Yegge's 8 stages are still the best individual-maturity model. The org that makes Stage 6+ work without burning out its seniors will be the one with IPETs and a working bad-day protocol.

Other perspectives
01Development·02Delivery Management·03Organization·04Infrastructure