An AI agent deletes a payments safeguard that existed because of a disaster. The pull request is green. The reviewer is junior. Nobody ever decided the agent was allowed to touch that service. It just could. The agent acted. Who answered?

The framework
Scope the authority. Keep the trace. Right-size the human checkpoints to blast radius. Give the agent memory. Red-team the whole thing. The agent acts, you answer.

Inside this episode

• Intake — Once agents act and chain decisions across your systems, "is this model accurate" stops being enough. The new question is what an agent is allowed to do, and who's accountable when it acts.
• Flow — The five-move control model: capability envelopes enforced at the infrastructure level, the trace, tiered human checkpoints, ADRs as the agent's memory of why, and governance red teams.
• Outcome — A model program runs the five moves in a quarter: ADR coverage 35% to 78%, agent-authored drift from ~62% to single digits, and the trace catches a near-miss before it ships.

Also inside
Gartner expects agents in 40% of enterprise apps by the end of 2026 and 150,000+ per Fortune 500 by 2028; non-human identities already outnumber humans roughly 80 to 1; and why one-size-fits-all agent governance actually backfires.

Links

• Full transcript & framework: rickpollick.com/blog/valuestream-episode-3-the-agent-acts-you-answer
• Show home: rickpollick.com/podcast

Next episode
Boundaries got us here. Next time it's capability: giving the agent a brain, the context, memory, and priorities that turn a confidently-wrong assistant into something that actually knows your week.

Subscribe in your podcast app of choice. New episodes monthly. Companion essay on the blog with each ship.

This is Valuestream. I'm Rick Pollick. The agent acts, you answer.

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 thesis
The 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 plan
Don'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 prescription
Two 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-hurts
• Episode 1 (See It, Own It, Move It): rickpollick.com/blog/valuestream-episode-1-see-it-own-it-move-it
• Show home: rickpollick.com/podcast

Next episode
The 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.

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 framework
See 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 inside
Why 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-it
• Heatmap template + Product Camp Pittsburgh deck: rickpollick.com/blog/not-my-problem-product-camp-pittsburgh-2026
• Show home: rickpollick.com/valuestream

Next episode
How 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.