By Marty Cagan · svpg.com · LinkedIn
Marty Cagan responds to a critique of the Spotify model of scaled Agile by arguing that the critic overlooks Spotify's business outcomes and Fitbit's decline after adopting the process the critic favored. He contends the real driver of Spotify's innovation is empowered product teams and especially empowered engineers, with autonomy set very high. He acknowledges the fair criticisms of weak management and leadership at Spotify, but argues these trade-offs were consciously accepted. He distinguishes outputs from outcomes and urges readers to focus on underlying principles rather than process details.
01Key takeaways
- Judge process changes by business outcomes and innovation, not only by output or delivery velocity.
- Empowered product teams and especially empowered engineers are the core driver of sustained innovation.
- High autonomy brings inefficiencies, so leaders should consciously accept those trade-offs and plan to strengthen management over time.
- Delivery-team models can increase output while reducing the innovation needed in competitive markets like wearables.
- Study the principles behind a company's success instead of copying its specific process or framework.
02Key sections
- Outcomes over process
- Cagan argues the critique ignores that Spotify built a highly valued company while Fitbit's value fell sharply after adopting a delivery-team process. He frames this as a clear case of output versus outcomes.
- What Spotify got right
- The core of Spotify's way of working is empowered product teams and empowered engineers with very high autonomy. This matters more than the Agile terminology and visuals that surround it.
- Fair criticisms and accepted trade-offs
- High autonomy paired with low management and leadership creates inefficiencies. Spotify's leaders knew this and judged the trade-off acceptable, while expecting to adjust as they grew.
- Fitbit's contrasting approach
- Fitbit moved to delivery teams instead of empowered product teams, which Cagan believes reduces innovation even if output rises. He notes the decline followed the change, though causation cannot be proven.
- Keep the perspective
- Cagan clarifies he does not personally advocate Spotify's scaled Agile process, but says it is still a strong model. Readers should look for deeper truths rather than copying process details.
03From the post
“A partnership dedicated to teaching best practices to product teams and product leaders”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.