The AI-Native IT Organization
What changes in the IT operating model when agents perform routine work: decision rights, roles, controls and metrics. The course includes a delegation framework, the DORA and METR evidence on AI productivity, and a 180-day plan.
L101Foundation·14 slides·About 13 minutes
L101Lead · Foundation
The AI-Native IT Organization
How the IT function changes when software agents carry a growing share of the work, and how to lead that change.
The premise
An AI-native IT function redesigns work, decisions and controls
Adding a copilot to each workflow can speed up individual tasks. Redesigning the workflow around what agents can now do reliably, and around what still requires human judgment, changes what the IT function can deliver.
What the evidence says
AI use is widespread, while measured gains vary
DORA finds that AI acts as an amplifier, magnifying an organization’s existing strengths and weaknesses.
of technology professionals surveyed by DORA reported using AI at work, and more than 80% believed it had increased their productivity.
DORA, State of AI-assisted Software Development, 2025
longer to complete tasks where AI was allowed, for 16 experienced open-source developers. Afterwards they estimated AI had cut their time by 20%.
METR randomized controlled trial, July 2025
of DORA respondents reported little or no trust in AI-generated code. DORA linked AI adoption to higher delivery throughput but lower stability.
DORA, State of AI-assisted Software Development, 2025
In February 2026, METR called its newer data “an unreliable signal”, as developers unwilling to work without AI opted out, but believed developers are likely more sped up than in early 2025. Measure gains in your own workflows.
The shift
Six shifts define the AI-native IT function
Delegation framework
Decide what to delegate by consequence and reversibility
Architecture of the work
Work moves across four layers
People
Roles shift toward specification, review and exceptions
New responsibilities appear in every team: owning each agent, evaluating it, managing its identity and curating the context it uses.
Decision rights
Write decision rights down before agents act
| Decision | Agent may | Approval | Evidence retained |
|---|---|---|---|
| Classify and route an incident | Act | None; outcomes sampled | Classification, confidence, outcome |
| Change an agent’s model, prompt or tools | Propose only | Agent owner, after evaluation passes | Versions and evaluation results |
| Patch a production system | Act after approval | Service owner or standard change | Change record, test results, rollback plan |
| Retire an application | Prepare evidence and the runbook | Business owner and architecture | Usage, dependencies, retention decision |
| Grant or elevate access | Provision approved requests only; never approve | Identity governance | Request and approval chain |
Control plane
One control plane for every agent
Decision rights hold only when they are enforced the same way for every agent, whichever team built it.
Maturity
Five stages from assisted to native
Moving to Delegated requires current context, controls enforced in the workflow and shadow results that meet thresholds.
Measurement
Six measures for delegated work
AvoidLicenses activated, prompts per user and lines of code generated count activity; report them only beside outcomes.
Pitfalls
Six common failure patterns in IT’s AI programs
Getting started
A 180-day plan
- Select three high-volume, reversible, measurable workflows
- Baseline cycle time, quality and cost
- Write decision rights and thresholds for each workflow
- Stand up agent identities, logs, evaluation and cost tracking
- Build current context for the systems in scope
- Run agents in shadow mode against human results
- Approve by exception where shadow results meet thresholds
- Publish results against the baseline
- Extend to the next workflows; adjust roles and funding
Summary
Key takeaways
- AI-native IT redesigns work around what agents do reliably and what still needs human judgment.
- Delegate by consequence and reversibility, and write decision rights down before agents act.
- Current, evidence-based context and enforced controls make delegation safer.
- Measure cycle time, stability, quality and cost per outcome; treat usage as context only.
- Start with three workflows, one control plane and a published baseline.
Further reading
- Announcing the 2025 DORA report: State of AI-assisted Software Development (opens in a new tab)Google Cloud, DORA research, September 2025
- Introducing DORA’s inaugural AI Capabilities Model (opens in a new tab)Google Cloud, DORA research, September 2025
- Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity (opens in a new tab)METR, July 2025
- We are Changing our Developer Productivity Experiment Design (opens in a new tab)METR, February 2026
- Our thesis: the next era of enterprise technologyAxiarete
- One of the greatest beneficiaries of agentic AI in enterprise IT: enterprise architectureAxiarete
Bring this course to your leadership team
We run private working sessions that apply these frameworks to your own estate, data and pending decisions.