Organization
How organizations adapt to the age of agents. From "buy licenses" to "agent fleet management".
Maturity →
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.
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.
July 2026 update: the labor picture from May held its shape into June.
AI was cited in 40% of May's announced layoffs (an all-time monthly high), and June brought concrete cuts - Oracle disclosed headcount down ~21,000 citing AI (June 22), ServiceNow and GitLab followed. But the deeper June story is that capability, not headcount, is the real lever. Anthropic reported Claude now answers 95% of its internal analytics queries - and the win came from skills and data governance, not a bigger model (accuracy went 21% to 95%+, and decays back toward 65% within a month if nobody maintains the skills). "Why AI hasn't replaced software engineers, and won't" (June 14) makes the same point from the other side: AI compresses the execute middle, not specification or accountability. Samsung reversed its 2023 GenAI ban and rolled ChatGPT + Codex out org-wide. Cutting humans before maturing the skill layer still creates a permanent capability hole.
Three role shifts crystallized. Review moved up the lifecycle - "AI Is Moving up the Software Lifecycle: from Code Review to PRD Governance" (June 24) shows Uber, DoorDash and Cloudflare using AI to evaluate specs before code. "Loop engineering" got a name and a theory (Addy Osmani, LangChain, Loopcraft) as the skill one floor above harness engineering. And a counter-discipline emerged: human-skill preservation - "when I reject AI code even if it works" (June 19), friction by design, and Craig McLuckie's "culture as a team's operating system" - guarding against cognitive surrender as deliberate org design, not personal willpower. On the debt side, a new lens arrived: Disposable Software and Sacrificial Architecture (a16z, Fowler) - when creation is near-free, some artifacts are built to be thrown away. The discipline is telling them apart from the durable systems where Agentic Technical Debt still compounds - and remembering that disposable code leaves durable side effects.