Ep. 2 — Trust the Number That Hurts: Metrics That Lie in the Agentic Era

Two leaders. Two trusted numbers. Two metrics that looked great and lied. Episode 2 of Valuestream walks the delivery metrics that were built for a pre-agentic world and quietly stopped working the moment agents started authoring code and dragging dependencies into your programs.The thesisThe cost of a metric that lies isn't that it's wrong. It's that it's confident. It walks into the board meeting, flashes green, and buys you another quarter of believing motion is progress.Inside this episodeIntake — Why DORA's four metrics and program-level critical path are both failing in the same way: the assumption that the thing producing the work is human has changed, and the math hasn't.Flow — The five-metric replacement layer for engineering (outcome latency, reviewer load, rework ratio, time to restore, production confidence) plus dependency density for programs (edges per node, with four edge types: code, data, process, people).Outcome — A composite case at 200 deploys/week reporting elite on every DORA number. Segmenting failure rate by author type showed agent-authored failure at 3x the human rate. Rework ratio hit 26%. The payments cluster had a dependency density of 3.4. We collapsed services, decoupled the integration, and cut the highest-edge scope. Density dropped to 1.9. Rework dropped to 9%. Deploy count went down on purpose. The program shipped on a date we could actually predict.The migration planDon't swap your dashboards overnight. Quarter one: instrument the new numbers next to the old ones without acting. Quarter two: add reviewer load and the confidence score, segment failure rate by author type. Quarter three: demote deploy frequency and critical path from headline to context.This week's prescriptionTwo spreadsheets. Pick one program. Segment last month's change failure rate by author type (human, agent assisted, agent authored). Score your three highest-risk clusters for dependency density. Look at the agent-authored failure number sitting next to the blended one you've been reporting. Trust the number that hurts.LinksFull transcript and frameworks: rickpollick.com/blog/valuestream-episode-2-trust-the-number-that-hurtsEpisode 1 (See It, Own It, Move It): rickpollick.com/blog/valuestream-episode-1-see-it-own-it-move-itShow home: rickpollick.com/podcastNext episodeThe governance version of this conversation. Once an agent authors a third of your changes and chains decisions across your systems, the old question "is this model accurate" stops being enough. The new question is "what is this agent allowed to do, and who's accountable when it acts."Subscribe in your podcast app of choice. Companion essay on the blog with each ship.This is Valuestream. I'm Rick Pollick. Trust the number that hurts.