The AI Productivity Paradox: Flow Metrics for Agentic Delivery

Every engineering team now has a version of the same conversation. Someone says the AI tools made us faster. Everyone nods, because it feels true — more commits land, more pull requests open, the day fills up. Then someone asks the harder question: faster at what? Did more actually reach customers, or did we just generate more work in progress? And the room goes quiet, because nobody has the number.

That quiet is the story of this year. It has a name now — the AI productivity paradox — and it is the reason we are starting this report.

Individual output is up. System delivery isn’t.

The individual gains are real and easy to see. One widely cited analysis found developers using AI assistants completing 21% more tasks and merging 98% more pull requests. If your dashboard measures activity, it is lighting up.

The system-level picture is where it gets uncomfortable. Google’s DORA 2025 report found teams adopting AI raising their deployment frequency and their change-failure rate at the same time. The blunt summary making the rounds: AI helped you build the wrong thing faster. DORA’s own framing is sharper still — AI amplifies the quality of the engineering system it operates within. A mature workflow converts the speedup into delivery. A weak one converts it into a faster mess.

So the interesting question was never “is AI making individuals faster?” It obviously is. The question is whether that speed survives the trip through your system — from the moment work is committed to the moment it is done. And you cannot answer it by watching individuals. You have to measure the flow.

Why measuring flow is genuinely hard

If flow were easy to measure, every team would already have the number. It isn’t, for three reasons that predate AI and got worse with it.

The instrumentation burden. A real value-stream view wants sophisticated measurement infrastructure, not point-in-time tracking. Lead time usually means manually linking tasks to commits, tagging pull requests, and stitching together tools that each hold a fragment of the timeline. The wiring rots the moment your workflow changes, which is often.

The fuzzy commitment point. Cycle time is only meaningful if you can say when a piece of work started. But most tools have no crisp moment where an idea stops being a maybe and becomes committed work. Without that boundary, “cycle time” quietly measures how long something sat in a backlog — which is not the same thing at all, and flatters or damns you at random.

Velocity theater. Optimize one flow metric and you can degrade another; push throughput and quality slips, or the reverse. Any single number, reported without its definitions, is an invitation to game it — a beautiful dashboard that means nothing, paved with cherry-picked medians.

Put those together and most “we measure our flow” claims turn out to be a burndown chart and a good feeling. That is the gap the AI paradox exposes: the tools that would tell you whether the speedup reached customers are the ones nobody quite finished wiring up.

Flow metrics are a feedback mechanism, not a scoreboard

Before the numbers, one framing that matters more than any of them. Flow metrics are worth having only if they change a decision. They are the input to questions you actually face: pull more work into progress or drain what’s already there? Is the backlog a healthy queue or a landfill? Did last week’s process change help? A metric that never moves a decision is decoration, however precise — which is the bar we hold this report to.

Measured by construction

Here is the move that makes this report possible. kanbento is an agent-native kanban board where every change is an event in an append-only log. That design choice, made for other reasons, has a useful side effect: the flow metrics are already there.

Every transition carries a timestamp, so cycle and lead time are a fold over data that already exists — nothing to instrument, nothing to keep wired. The commitment point is a first-class concept, an explicit boundary work crosses, so “when did this start?” has a real answer and cycle time is well-defined. Rework loops are counted because a loop is a recorded event, not a guess. And because the pool, the board, and the knowledge layer share one log, the system-balance view — how much came in versus how much went out — is just arithmetic over arrivals and departures.

The point isn’t a feature. It’s that the numbers are a property of how the work is recorded, so they can’t drift away from reality the way a hand-maintained dashboard does. Which means we can publish them — with their definitions — and let you check our work.

Our week, measured

So here is the first one. This is issue #1 of an ongoing report, with more to come: the flow of our own board, in the open, method included.

The measurement. Card types counted for delivery timing are substantive work only — features and bug fixes. The window spans the board’s four active weeks so far (W26 through W29). Where a distribution matters we lead with the 85th percentile (p85), not the median, for a reason we’ll come back to.

Throughput — cards delivered per week:

Week	Delivered
W26	3
W27	38
W28	20
W29	29

The ramp is the headline. A near-standing start, a spike as the flow opened up, then delivery settling into a steady 20-to-30 cards a week. That plateau is healthier than the spike — a rate you can sustain beats a number you hit once.

Flow balance — is the system draining or filling? All-time, 252 cards captured against 90 delivered: a net of +162. The system is filling. More is arriving than leaving, and the backlog is growing upstream. On its own that is neither good nor bad — a filling system is what ambition looks like early — but it is the number we will watch hardest, because a system that fills forever is a system that never ships what it promised.

Cycle time — commit to done. Median 8 minutes; p85 1.4 hours. Lead time — capture to done. Median 1.2 hours; p85 27 hours. The pipeline is clean: a single rework loop across all 90 delivered cards, and a 6% discard rate — the share of arrivals abandoned or triaged out before delivery, which is upstream selection working, not waste.

The honest part

Now the definitions, because this is where most reports quietly cheat.

That 8-minute median cycle time is flattering, and we will not headline it. Plenty of small chore cards are committed and finished in the same minute, and they drag the median down toward zero. It is a true number that tells you almost nothing about substantive work. The p85 is the honest headline — 85% of committed work reaches done inside 1.4 hours — paired with the throughput curve, which no single-point statistic can hide behind.

This is the discipline the AI paradox demands. It is easy to find a chart that says your agents made you faster. It is honest work to report the one that shows where they didn’t. Our lead-time p85 of 27 hours, against a 1.2-hour median, says exactly that: most work moves fast, and a real tail of it sits, waiting, for far longer than the median lets on. That tail is our next problem. Naming it is the point of measuring at all.

What this report is

We’ll keep sharing these because a single snapshot proves nothing and a trend proves a lot. The format will stay fixed — throughput, flow balance, cycle and lead time, and the honesty note that states our definitions — so that over time you are reading a trend, not a highlight reel. When a number moves, we will say why. When one embarrasses us, we will still print it.

If you have read our piece on why a living spec needs a board, not a better template, this is the same idea pointed at delivery instead of intent: the thing that keeps you honest isn’t a better dashboard, it’s a system where the truth is recorded as it happens and can’t be quietly edited afterward.

In a future issue we will show you whether the system is still filling — and what we did about it. If you want the same numbers for your own team, the shortest path is a board where they’re a property of the work rather than a project you have to staff: that’s what kanbento is, and where this report comes from.