Agility is Inefficient
summary
Argues that agility must prioritize effectiveness over efficiency and gives concrete signs and fixes: four warning smells are budgets and cost cutting, process-centric leadership, deep specialization, and utilization maximization. Uses Blockbuster (peak ~9,085 stores and ~85,000 employees, missed buying Netflix for $50M), Nokia (missed iPhone 2007), and Tesla vs Volkswagen (Tesla +846% over five years vs VW stagnant) as evidence. Offers practical hacks—add adoption and flow metrics to status reports, pair a team member with the specialist until they do ~50–60% of the work, and use containment tactics like low‑priority backup tasks to preserve flow.
AI-written summary · about
chapters (15)
- 0:00Intro
- 5:16Goal
- 7:21Effectiveness vs Efficiency
- 15:47First example
- 21:00Second example
- 25:45Third example
- 30:17Four warning signs
- 34:40The art of delivering twice the value in half the cost
- 35:38Q&A
- 36:19Special twist
- 39:11Hack budgets
- 41:34Contain specialism
- 43:32Contain under utilization
- 45:58Effectiveness over efficiency
- 46:43Outro
related talks
49mAgility is Inefficient
01h 31mAgility ≠ Speed - Agile Development
35mAgility ≠ Speed
46mAgility and Architecture Together – Enabling a Fast Flow of Change
52mAgility ≠ Speed
44mAgility ≠ Speed
34mFor effectiveness, Agile was never the answer
01h 04mIs Agile Still the Answer? Lessons from Real World Agility