Why engineering teams fail to extract value from AI coding agents and the four things to fix, in order.
AI does create surface level slack. 97 minutes saved per week from summarisation features alone. But while this surface adoption is easy, deep transformation is not. 88% of organisations use AI somewhere. Only ~6% achieve high-performer status with meaningful delivery impact. The four levels below explain why.
Software has unit tests, CI/CD, DORA metrics. The AI development system including your AGENTS.md, your skills, your compound engineering workflow, your agent instructions has none of that. When you change something, you have no systematic way to know if it helped, hurt, or made no difference.
The engineer's job has moved upstream. It no longer lives in writing code. It lives in writing specifications, defining evaluation criteria, and directing agents. Engineers still acting as coders are not slower at the new job, they are doing the wrong job entirely.
Agents can only act on what is explicitly documented. The tribal knowledge in people's heads, the architecture decisions made in Slack threads, the conventions assumed but never written are all invisible to the agent. When it can't find context, it hallucinates confidently. And a codebase optimised for human navigation is hostile to agent operation.
Engineering teams run at ~98% utilisation. Queue theory is precise: as utilisation approaches 100%, wait times approach infinity. Improvement tasks queue indefinitely. The team never reaches the productive state or arrives there superficially and makes things worse. This is not a culture problem. It is a mathematical property of loaded systems.
The bottleneck is never the model.
The bottleneck is the harness,
the structured environment around it.
Everyone can buy the same models. What you cannot buy is the operating environment your team has built: protected capacity to learn, documented processes agents can act on, engineers who design systems rather than write lines, and eval infrastructure that verifies whether any of it is actually getting better. That harness is the structure that compounds and is hard to copy.
| Level | The question to ask | The honest answer in most orgs |
|---|---|---|
| L1 : Zero Slack | Do we have protected time specifically for AI coding adoption? | No. It competes with sprint commitments. |
| L2 : Invisible Process | Could an agent, given our repo, do meaningful work without asking anyone? | No. It would hallucinate half the context. |
| L3 : No Coders | Are engineers writing specs and eval criteria before starting agent tasks? | No. They're still prompting to get code. |
| L4 : Eval Engineering | When we change our agent configuration, do we know if it improved? | No. We assume. We don't test. |