By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that slow product delivery is usually not caused by weak developers but by organizational and process problems. Drawing on his work with many product teams, he lists the ten most common root causes of slow velocity. The top causes include weak product ownership, missing strong project management, infrequent release cycles, and excluding lead engineers from discovery. He also flags unclear vision, non-dedicated teams, mixing sustaining work with new development, technical debt, and a lack of holistic system understanding. The piece matters because it reframes velocity problems as fixable structural issues rather than individual shortcomings.
01Key takeaways
- Look to product ownership and project management before blaming developer skill for slow delivery.
- Release at least every two weeks, backed by regression and release automation.
- Bring lead engineers into product discovery from day one to surface faster approaches.
- Finish UX design before backlog items are scheduled to avoid waiting and churn.
- Keep teams dedicated and separate sustaining work from forward progress work.
- Maintain a clear product vision and a holistic view of how team efforts fit together.
02Key sections
- Ownership and management roles
- Cagan names the absence of a strong product owner as the biggest slowdown, with weak project management a close second. He stresses that the project manager should be a dedicated person who actively removes impediments.
- Release and engineering practices
- Slow release cadence and missing test and release automation hold teams back. Lead engineers should join discovery early so faster technical alternatives can shape the solution.
- Design and discovery timing
- UX design should be finished before items reach the backlog, otherwise teams wait on designs and churn. Clear product vision and stable priorities prevent wasted rework.
- Team structure and interruptions
- Reassigning engineers constantly erodes expertise and relationships, while mixing support escalations with new work dramatically reduces throughput. A separate rapid response team can absorb interruptions.
- Architecture and holistic view
- Rigid architecture and accumulated technical debt limit how fast a product can evolve, and teams need a shared understanding of dependencies to avoid thrashing.
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.