Valuestream

Rick Pollick

A podcast from Rick Pollick on how modern companies actually turn strategy into shipped software. Every episode walks one real story through three segments — intake, flow, outcome — covering operating models, platform engineering, and agentic-AI patterns that move value from the roadmap to production. 25 to 35 minutes, monthly. No vendor pitches. Focus is the operating model, not the tool stack. Companion essays at rickpollick.com/blog.

Episodes

  1. 5d ago

    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 episode Intake — 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. Links Full 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.

    20 min
  2. May 25

    Ep. 1 — See It, Own It, Move It: Where Value Actually Flows

    The launch episode of Valuestream. Nine senior people in a room, forty-five minutes blocked, one decision on the table — and nobody makes it. This is the quietest failure mode in modern delivery, and the three-word fix you can ship in a Google Sheet on Monday. The frameworkSee it. Own it. Move it. Visibility is the intervention. One name per decision. Every decision gets a date — not the ship date, the decide date. Inside this episode Intake — three quiet failure modes (handoff theater, update chasing, decorative dashboards) and what decision latency actually costs you ($50K per incident; $3,750 per employee per year in lost productivity per McKinsey).Flow — wiring Owner-Decision-Date into a product-team operating model, an internal developer platform, and an agentic-AI strategy that survives 2027 (Gartner: 40% of agentic AI projects will be cancelled by end of 2027 — the cause is organizational, not technical).Outcome — a 60% drop in decision latency in two weeks (51 days → 19), a platform team that took mean-time-to-production from 14 weeks to 3, and an agent metric change that doubled effective throughput.Also insideWhy 80% of large engineering orgs will have a dedicated platform team by end of 2026 (Gartner) and what most are getting wrong. Trust calibration, hybrid workflows, and feedback loops for agentic AI. Why 97% of orgs have hit an AI security incident and what governance actually needs to cover now. The five-step re-baselining conversation that turns a slipping program back into a managed one. Links Full transcript & framework: rickpollick.com/blog/valuestream-episode-1-see-it-own-it-move-itHeatmap template + Product Camp Pittsburgh deck: rickpollick.com/blog/not-my-problem-product-camp-pittsburgh-2026Show home: rickpollick.com/valuestreamNext episodeHow to introduce decision visibility when your culture punishes visibility — every CFO has nodded at the heatmap and then said "I can't show this to my CEO." Subscribe in your podcast app of choice. New episodes every other week. Companion essay on the blog with each ship. This is Valuestream. I'm Rick Pollick. See it, own it, move it.

    26 min

About

A podcast from Rick Pollick on how modern companies actually turn strategy into shipped software. Every episode walks one real story through three segments — intake, flow, outcome — covering operating models, platform engineering, and agentic-AI patterns that move value from the roadmap to production. 25 to 35 minutes, monthly. No vendor pitches. Focus is the operating model, not the tool stack. Companion essays at rickpollick.com/blog.