Capability 01 of 04 · Organization
AI Adoption Model
How your organization rolls out AI tools - from individual experiments to org-wide strategy.
5
maturity levels
15
practices
15
guides
L1 · Stage 01Ad-hoc
Practices - what it looks like3 guides
- Adoption via bulk license purchaseThe big-bang license purchase is the most common first move in enterprise AI adoption, and the most reliable predictor of failure.guide→
- Initial enthusiasm fades to low usageEnthusiasm → Silence → Shelfware is the name for the failure arc that almost every unstructured AI tool deployment follows.guide→
- Powerful tools on an unprepared processThe Ferrari Engine in Fiat 126p is a metaphor for a specific and common failure pattern: installing powerful AI capability into an engineering process that cannot take advantage of it.guide→
Criteria - what to measure
- 01AI tools have been adopted (licenses acquired)
- 02Adoption is tracked informally
- 03At least some developers are experimenting with AI tools
- 04Organization has not banned AI tool usage outright
L2 · Stage 02Guided
Practices - what it looks like3 guides
- Pilot teams (2-3 teams)A structured pilot is the antidote to the big-bang license deployment.guide→
- Internal championThe internal champion is the single most important structural element of a successful AI adoption program.guide→
- Pilot metrics; track cost-per-merged-PR from day onePilot metrics are the set of measurements you define before a pilot starts that determine whether the pilot succeeded and whether to expand.guide→
Criteria - what to measure
- 012-3 pilot teams are designated with explicit AI adoption goals
- 02An internal champion (or AI lead) is identified and has allocated time for the role
- 03Pilot metrics are defined and tracked (adoption rate, usage frequency, developer satisfaction)
- 04Pilot results are shared with the broader organization
- 05Champion has direct access to leadership for escalation
L3 · Stage 03Systematic
Practices - what it looks like3 guides
- Platform team owns AI toolingWhen AI tool adoption is owned by individual champions or informal volunteers, it scales up to a point and then stops.guide→
- Internal Developer Platform with AI layerAn Internal Developer Platform (IDP) is the set of self-service tools, workflows, and infrastructure that product teams use to build, test, and deploy software without requiring maguide→
- Standardized agent setup per team; "bad day protocol" - documented rollback when models or harnesses regress, plus a vendor-exit plan (Fable 5 vanished worldwide in 72h)A standardized agent setup means that every team starts from the same baseline agent environment - the same tools available, the same context injection approach, the same permissioguide→
Criteria - what to measure
- 01Platform team formally owns AI tooling (selection, provisioning, security, baseline configuration)
- 02Internal Developer Platform includes an AI layer (standardized agent setup, self-service provisioning)
- 03Standardized agent setup exists per team (every team has a working AI environment by default)
- 04New developer onboarding includes AI tool setup that completes in under 30 minutes
- 05Platform team tracks adoption breadth (% of developers with active AI setup)
L4 · Stage 04OptimizedMost teams aim here
Practices - what it looks like3 guides
- AI-first development culture (Samsung reverses 2023 ban for ChatGPT+Codex; wins come from skills + data governance, not a bigger model - Anthropic 95% internal analytics)An AI-first development culture is one where agents are the default approach to development tasks, not an option that some developers use sometimes.guide→
- Agent fleet management as disciplineAgent fleet management is the practice of treating multiple concurrent AI agents as a managed resource pool, applying the same operational discipline to agent orchestration that maguide→
- Developer = agent supervisor (Yegge Stage 6-7)In Steve Yegge's model of AI adoption stages, Stages 6 and 7 represent a fundamental shift in what a developer does.guide→
Criteria - what to measure
- 01AI-first development culture: 80%+ of developers use AI tools daily
- 02Agent fleet management is a recognized discipline with defined practices
- 03Developer role has shifted toward agent supervision (Yegge Stage 6-7)
- 04"Span of control" metric is tracked (how many agents a developer can effectively supervise)
- 05Organization benchmarks against industry AI adoption data (Zapier 97%, Cursor 3 adoption rates)
L5 · Stage 05Autonomous
Practices - what it looks like3 guides
- "Kubernetes for agents" - centralized orchestration"Kubernetes for agents" describes the centralized orchestration infrastructure that enables large-scale agent deployment across an organization - analogous to how Kubernetes manageguide→
- Human-at-the-wheel, not human-in-the-loop"Human-in-the-loop" describes an approval model where humans review and approve individual agent actions before they execute.guide→
- Organization optimized for agent throughput, not human throughputOrganizations are designed around assumptions about how work gets done.guide→
Criteria - what to measure
- 01Centralized agent orchestration system exists ("Kubernetes for agents")
- 02Developer role is "human-at-the-wheel" (strategic direction, not task-level involvement)
- 03Organization is optimized for agent throughput, not human throughput (meetings, processes, tooling all agent-aware)
- 04Agent orchestration system handles scheduling, resource allocation, and failure recovery
- 05Organization measures agent utilization as a key infrastructure metric
From the Field
Recent releases, projects and discussions the AI Radar classified into this capability.
discovered
An orchestration runtime for multi-agent AI systems. Declare agents, tools, and policies as YAML; Orloj schedules, executes, routes, and governs them for production-grade
discovered
Open-source workspace protocol for AI agent systems. If OSA / Claude Code is the employee, Canopy is the office.
discovered
Your AI agent skills, finally organized. A macOS app to browse, edit, and manage skills across Claude Code, Cursor, Codex, Windsurf, and Amp.
release
article
Kelsey Hightower: What the AI Hype Machine Won't Tell You
article
QCon London 2026: Team Topologies as the ‘Infrastructure for Agency’ with AI
article
Codex now offers more flexible pricing for teams
release
Which level is your team at in AI Adoption Model?
The criteria above are what we check in a facilitated assessment. Run it yourself to place this capability, see which gates you have passed, and compare it against the other 3 in Organization.
Start the assessment →