By Marty Cagan · svpg.com · LinkedIn
Marty Cagan and Jeff Patton argue that product teams should be judged by the outcomes they generate rather than the output they ship. The article offers a practical checklist of questions to diagnose how strong a product team is across staffing, team context, discovery, and delivery. It is aimed at leaders and teams still learning strong methods, helping them locate gaps and decide where to focus improvement. The questions serve as a diagnostic rather than a rigid standard, since cultural elements also matter for turning a good team into a great one.
01Key takeaways
- Judge product teams by the outcomes they generate, not the volume of output they produce.
- Make sure the team includes a strong PM, a strong designer, and a senior engineer engaged in discovery.
- Test several meaningful ideas each week, validating with real users and business stakeholders before building.
- Use MVPs, low- and high-fidelity prototypes, and live-data prototypes to validate ideas quickly and cheaply.
- Release at least every two weeks, instrument everything with analytics, and review KPI impact right after release.
02Key sections
- Outcomes over output
- The authors start from the principle that teams should be evaluated by the results they produce, not by how much they build. This sets the lens for everything that follows.
- Team staffing and chemistry
- A strong team needs a capable product manager, a strong designer for user-facing work, a senior engineer engaged in discovery, and co-located members who collaborate well.
- Team context
- Teams should have clear business KPIs, a shared vision, direct access to users and customers, and an understanding of key stakeholders and their concerns.
- Dual-track discovery
- Teams should test many meaningful ideas weekly using quick validation methods like MVPs and prototypes, kill weak ideas early, and run mini-retrospectives to learn faster.
- Dual-track delivery
- Teams should release frequently, resolve impediments quickly, automate testing, instrument analytics, and review KPI impact after every release and sprint.
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.