By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that no single product management model fits every company; the right one depends on context, and it is best chosen by starting from the problems a company is actually experiencing. Drawing on his work with high-tech companies, he lists ten frequent complaints, including wasted release cycles, slow time to market, lack of innovation, unhappy customers, and poor decision making. He frames each as a symptom of deeper problems in how products are produced. The practical implication is that an effective model must address these root causes and institutionalize better behaviors and processes, not just patch the symptoms. This sets up the factors he plans to explore in later articles.
01Key takeaways
- Diagnose your company's specific product challenges before choosing or changing a product management model.
- Treat wasted release cycles and slow time to money as signals that releases are not achieving their objectives.
- Recognize that unhappy customers can persist in business software because of high switching costs and split purchase and usage roles.
- Watch for decision-making churn, where shifting requirements prevent forward progress, as a sign of process breakdown.
- Address root causes such as unclear roles and culture, since symptoms like low morale often stem from them.
- Build processes and behaviors into the organization so improvements last beyond individual techniques.
02Key sections
- Starting from the problems
- Cagan begins by asking companies about their specific challenges rather than prescribing a model. This diagnostic approach frames the rest of the piece.
- Symptoms of product delivery trouble
- A list of ten common complaints covers wasted releases, slow time to market, weak innovation, unhappy customers, and difficulty replicating success. Each reflects how the company builds products.
- Organizational and people issues
- Growth, customer-specific special requests, decision-making breakdowns, role confusion, and low morale signal structural and cultural problems behind the product process.
- Symptoms versus root causes
- Cagan stresses that these complaints are symptoms, so the best model must institutionalize appropriate behaviors and processes rather than offer quick fixes.
03From the post
“A partnership dedicated to teaching best practices to product teams and product leaders”
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.