By Marty Cagan · svpg.com · LinkedIn
Cagan and Moore argue that 'transformation' is often described with labels like Agile or product-led, which fail to capture what actually changes. They propose defining transformation by three concrete shifts: how a company builds and deploys, how it solves problems, and how it decides which problems matter. Successful transformations are rare, so lessons from them are especially valuable. The framing matters because leaders who chase labels rather than changed behaviors often end up with 'fake agile' and feature teams that look modern but don't improve outcomes. The three shifts can run in parallel through pilot teams rather than as a strict sequence.
01Key takeaways
- Define transformation by concrete behavior changes, not by adopting a methodology label like Agile.
- Aim for releases at least every two weeks; continuous delivery is the stronger goal.
- Give product teams problems to solve rather than pre-chosen features, and build discovery skills.
- Treat strategy and vision as the hardest and most impactful part: choose which problems deserve attention.
- Run the three changes in parallel through pilot teams, then expand gradually.
- Invest in product leadership skills and coaching, since transformation depends on strong leaders.
02Key sections
- Defining success
- The authors note that the real question is what transformed companies do better, and that outcome-oriented answers focus on responding to threats and seizing opportunities. Labels like 'Agile' are judged insufficient on their own.
- Changing how you build and deploy
- Moving from quarterly big-bang releases to continuous delivery, or at least true releases at least every two weeks. Agile is often the forcing function, though it isn't strictly required.
- Changing how you solve problems
- Shifting from stakeholder-prioritized feature roadmaps to empowered product teams assigned problems, using discovery to find solutions that are valuable, usable, feasible and viable. This also changes the relationship with stakeholders into a collaborative one.
- Changing how you decide which problems to solve
- Deciding which threats and opportunities to pursue is described as the most profound change, driven by a compelling product vision and insight-based product strategy tied to business objectives.
- Leadership and sequencing
- Strong product leaders are essential, and coaching may be needed. The three changes are best pursued in parallel with pilot teams, then expanded across the organization.
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.