From Output to Outcome: How AI Forces a Rethink of Teams, Leadership, and Value

Scrum.org
Scrum.orgJun 11, 2026

Why It Matters

The shift from output to outcome equips companies to turn AI‑driven productivity gains into measurable business value, redefining team structures and leadership priorities for the digital age.

Key Takeaways

  • AI amplifies code production, shifting scarcity to abundance.
  • Product operating models enable faster AI adoption than waterfall.
  • Outcome loop links outputs to customer and employee value.
  • New constraints shift from development to governance and backlog planning.
  • Teams can deliver ten‑to‑hundred‑fold more value with AI agents.

Summary

The podcast introduces Mick Kirsten’s new book, Output to Outcome, which argues that AI forces organizations to move beyond traditional output‑centric metrics and redesign teams, leadership, and value streams. Building on his earlier work, Project to Product, Kirsten shows how product‑operating models—end‑to‑end agile structures—are uniquely positioned to harness AI’s amplification capabilities.

Data from dozens of enterprises reveal that only about 8% of the end‑to‑end delivery time resides in development teams. Even if those teams become five‑times faster, bottlenecks upstream and downstream will dominate. AI can dramatically increase code generation, but without an outcome‑focused feedback loop, the extra output does not translate into customer or employee value. The book proposes an “outcome loop” that ties strategy and budget (inputs) to team artifacts (outputs) and measures real outcomes for users and staff.

Kirsten cites real‑world examples, such as a large Dutch bank grappling with AI ROI, and warns against easy‑to‑measure proxies like token consumption or lines of code. He stresses that the classic scarcity of developer capacity is disappearing, shifting constraints to governance, trust, and backlog prioritization. The theory of constraints remains relevant, but the limiting factor now moves from code creation to strategic planning and risk management.

For leaders, the implication is clear: adopt product‑operating models, embed outcome loops, and re‑engineer governance to keep pace with AI‑augmented teams. Doing so can enable a single scrum team, augmented by AI agents, to deliver ten‑to‑hundred‑fold more value than traditional setups, fundamentally reshaping how organizations create and capture value.

Original Description

Dave West sits down with Mik Kersten, author of Project to Product and the upcoming Output to Outcome (https://www.amazon.com/dp/1966280238?ref=cm_sw_r_ffobk_cp_ud_dp_Y8P7MK8KD3KBQWA55E2R&ref_=cm_sw_r_ffobk_cp_ud_dp_Y8P7MK8KD3KBQWA55E2R&social_share=cm_sw_r_ffobk_cp_ud_dp_Y8P7MK8KD3KBQWA55E2R&bestFormat=true) , to explore why AI amplification is exposing the real bottlenecks in how organizations work. Mik shares data from over 3,600 value streams showing that development teams account for just 8% of end-to-end delivery time which means making those teams faster with AI doesn't move the needle if the constraints are upstream and downstream.
The conversation digs into why most organizations are measuring the wrong things (hint: token consumption is not a productivity metric), why overlay agile structures have largely failed, and why the answer isn't fewer teams it's more empowered ones. Mik introduces the core models from his new book: the outcome loop, the outcome tree, and seven organizational shifts that together make up a new operating model designed for the age of AI.
Key Takeaways:
• The bottleneck has moved from software delivery to planning, governance, and innovation and most organizations haven't caught up
• Making development teams faster with AI delivers little value if the surrounding system isn't designed around outcomes
• Agile as an overlay structure doesn't work it has to become the primary operating model and the actual org chart
• Empowered, autonomous teams are not optional in an AI-driven world the speed of feedback loops makes half-measures unsustainable
• Leadership roles need to be redefined and incentive structures realigned to match the way teams are actually working
• The theory of constraints still applies in the age of AI the constraint just keeps moving, and finding it is now the critical management skill
Links

Comments

Want to join the conversation?

Loading comments...