AI Measurement: Shift Harness's collection on DORA metrics. Expect field-tested guidance on DORA metrics, written for CTOs and delivery teams.
AI Adoption
Most AI programs stall around month nine because nobody can show the board what actually changed. A five-rung ladder that places an org by the artifacts it produces - PRs, ADRs, test plans, postmortems - and names the missing operating asset at each rung.
Quality Harness Engineering
There is a number most CTOs cannot explain. Output volume is up, adoption is healthy, and the delivery metric that was supposed to move has not. The productivity did not disappear. It relocated.
AI operating model
The strange part isn't that the win is small. It's that the win is missing. The coding got faster, and the time from request to customer stayed exactly the same.
Quality Harness Engineering
The dashboards look like a win: PRs merged up, cycle time down, adoption climbing. Then the same leaders say delivery feels flat and quality feels thinner. That gap is the subject.
Quality Harness Engineering
Your engineers ship more code than ever, adoption is high, and delivery has barely moved. The instinct is to read that as an adoption problem. It is an accounting one.
AI Measurement
Self-report drifts upward and license counts measure procurement, not practice. The signal that holds up is the artifact each role produces every week, read on a ladder from exists to outcome.
AI Measurement
The survey says the team is well along. The license dashboard says every seat is active. Then you open last sprint's pull request and it reads exactly like a year ago. Here is how to profile what actually changed, role by role, from the artifacts.
AI Measurement
A controlled trial put the gap at 39 points: developers felt 20% faster while measuring 19% slower. The survey samples a feeling, not your delivery system. Here is what to instrument instead.
AI Measurement
A delivery team turns on AI coding tools. The deploy-frequency line climbs within a quarter. And in that same quarter, the change-fail rate climbs too. DORA 2025 found both numbers rising together in the same teams. AI does not improve a delivery system.
AI Measurement
The CTO's velocity chart is flat. The team is shipping noticeably bigger scopes per ticket. Both numbers are true, and both come from the same backlog. Story points are a relative unit. AI changed what fits inside one. Reading flat velocity as flat productivity is reading the wrong instrument.
AI Measurement
Eighteen months into the agentic-coding wave, the question CTOs are asking has shifted from which tool to why the delivery numbers have not moved despite real adoption and real developer speed gains.
AI Measurement
Most open with license count: a procurement number dressed up as a transformation metric. Here is what an honest dashboard drops, what it tracks instead, and why it is really a decision about your operating model.