Maturity Matrix
Matrix/Development

Development

How developers work with AI day-to-day. From sidebar chat to fleet agents.

4capabilities20levels60practices60guides
The matrix · full map
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·15 guides
Coding Agent Usage
How your team uses AI coding assistants - from autocomplete to autonomous agent fleets
Autocomplete and a chat window
3 practices·3 guides
An agent in the IDE, rules in the repo
3 practices·3 guides
CLI agents become the primary interface
3 practices·3 guides
Agents run unattended, in loops, on schedule
3 practices·3 guides
A fleet ships faster than you can read
3 practices·3 guides
02·15 guides
Context Engineering
What information agents receive about your codebase, architecture, and conventions
The agent sees one open file
3 practices·3 guides
CLAUDE.md tells it the basics
3 practices·3 guides
Context is served, not scavenged
3 practices·3 guides
The org pushes context to the agent
3 practices·3 guides
Context maintains itself
3 practices·3 guides
03·15 guides
Code Review & Quality
How AI-generated code is reviewed, validated, and approved before merging
Humans review everything, slowly
3 practices·3 guides
AI suggests, humans still decide
3 practices·3 guides
Lint is architecture; AI takes first pass
3 practices·3 guides
Green means merge - no human needed
3 practices·3 guides
Human eyes only on Red
3 practices·3 guides
04·15 guides
Testing Strategy
How tests are written, maintained, and validated in an AI-assisted workflow
Tests by hand, flakes by habit
3 practices·3 guides
Agents write tests, humans own the oracle
3 practices·3 guides
Requirements are the oracle, not the code
3 practices·3 guides
A red test means a real defect
3 practices·3 guides
The suite heals itself
3 practices·3 guides
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.

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

The July 2026 zeitgeist is bring it home.

After May's invoice, June was the month teams went looking for a way to depend on AI without being owned by it - and the case for sovereignty made itself. On June 9 Anthropic launched Fable 5 and Mythos 5, its most capable models ever; on the evening of June 12 it disabled them worldwide under a US export-control order, and they were still dark over a week later. Whatever you built on top of Fable 5 stopped working overnight, through no fault of your own. The most capable model is worth less than the model you can still run tomorrow.

The alternative got real the same month. Open-weight coding models crossed the line from toy to tool: GLM-5.2 (Z.ai, MIT) beat GPT-5.5 on SWE-bench Pro at a sixth of the cost, and Kimi K2.7-Code shipped with day-one vLLM/SGLang support - both runnable on your own hardware. The job is still decomposition and oversight, but now part of the job is deciding where the agent runs and what it is allowed to remember. Two June shifts matter here: memory moved beyond RAG (Anthropic dropped vector search in Claude Code for agentic grep, and Microsoft's FastContext repo-explorer subagent cut coding-agent tokens up to 60%), and review moved past pass-rate (FrontierCode found over half of SWE-bench results are "unmergeable slop" and scored even Opus 4.8 at 13.4% on mergeability). Keep held-out oracles, score mergeability not green checkmarks, and reject code you cannot understand even when CI is green. The harness is the part you own - and in June the field finally named the discipline of building it. After a year of "AI-native engineering," the cascade became explicit: prompt → context → harness → loop engineering (Addy Osmani, LangChain, Loopcraft), with two dozen-plus loop and meta-harness tools shipping in the month. That is the second half of sovereignty: when the model is swappable, the loop you stack around it - play, test, fix, verify, improve - is where your leverage actually lives.

Other perspectives