Our AI Coding Numbers Were Perfect. We Were Shipping Slower.
· Enterprise AI · 8 min read
Every AI dashboard was green. Delivery was slower.
The analysis
Adoption dashboards measure the thing that is easy to instrument: suggestions accepted, seats active, lines generated. None of those are delivery. A team can raise every one of them while the interval between a commit and a customer benefiting from it gets longer.
The mechanism is not mysterious once you look at where the work moves. Generation is cheap, so more code enters the pipeline. Review capacity does not scale with it. Reviewers face larger diffs that they did not write and cannot skim by intuition, so review either slows down or becomes shallower. Shallow review shows up later as defects, rework and incident time — costs that land in a different quarter and a different team's metrics than the tool that caused them. The dashboard stays green because it is measuring input volume in a system whose constraint has quietly moved downstream.
The fix is measurement discipline rather than tooling retreat. Report change lead time, change failure rate, review latency and rework share on a specific workflow before and after adoption, and insist that the comparison covers the same workstream rather than a favourable subset. If a tool genuinely helps, those four numbers move. If only acceptance rate moves, what you have bought is activity.
For engineering leaders being asked to justify AI spend, this reframing is the difference between a defensible business case and a story that collapses the first time a CFO asks what changed in the release cadence.
Full essay on Substack: Our AI Coding Numbers Were Perfect. We Were Shipping Slower..
More on Enterprise AI
- What the Stanford 2026 AI Index Actually Says
- From Ownership to Access — And Perhaps Back Again
- The Indian IT Debate Everyone Is Having Is the Wrong One
Discuss this with Prasanna: pw@prima-partners.com · book a 30-minute call.