From Agile to Outcome-Driven
summary
Argues that Agile alone rarely delivers value because organisations prize visible efficiency over hidden effectiveness, noticing only 1–2 customers in 15 years truly demand outcomes. Shows concrete failures: a firm cuts a product portfolio from ~66 to 8–9 products instead of just adding teams, vaccination services break when policy changes because multiple apps are unmanaged, and procurement kills opportunities with 6–9 month contract delays. Recommends outside‑in design, metrics tied to decisions, portfolio Kanban/flight levels and lean procurement.
AI-written summary · about
chapters (10)
- 0:00Agile to outcome-driven intro
- 2:53Agile effectiveness misses
- 6:47Empowerment in Agile role
- 10:18Continuous improvement flaws
- 13:03Data-driven decisions in Agile
- 16:34Agile scaling dependencies
- 20:27Strategic agility beyond teams
- 22:32Procurement HR Agile barriers
- 25:20Agile trend future
- 28:08Conclusion call for agility
related talks
43mNobody needs an Agile Transformation
43mAgile Outside Technology
49mAgile is a Dirty Word
03mAgile is a disaster today!
36mOne Agile Transformation and two beers please
01h 01mHow Agile Screwed Up Product Ownership and 5 Things You Can Do to Fix It
02mFor Agile to work you need to get measurable feedback
26mAgile Version 2016