By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that product teams should actively seek out critical, negative feedback, since qualitative insight about why users don't adopt, buy, or stay is more valuable than most quantitative data. He observes that teams routinely avoid this feedback and walks through the excuses he hears most often. For each excuse he offers a coaching response: detach ego from the product and fall in love with the problem, prioritize outcomes over output, treat feedback as a tool for learning rather than proof, and build ownership in place of mercenary feature-team behavior. The piece matters because a team that won't hear bad news will ship products that fail to serve customers.
01Key takeaways
- Build and test a prototype with real users early, before you become attached to the idea.
- Fall in love with the problem, not your solution, so criticism lands as information rather than rejection.
- Celebrate negative feedback when you get it, and aim to collect it weekly.
- Treat qualitative feedback as a source of insight about customers, not as evidence for or against your idea.
- Judge the team by outcomes achieved, not by shipping on a date that yields an empty victory.
- Build a sense of ownership in the team so that they care whether customers actually succeed with the product.
02Key sections
- The Truth Hurts
- Negative feedback stings most when people feel personally tied to what they built. Cagan advises seeking feedback early, falling in love with the problem rather than a specific solution, and making critique a normal team rhythm.
- There's No Time
- Teams fixated on deadlines may suppress any discussion that threatens a date, preferring a failed effort to a missed date. Cagan counters with the idea of empty victories and high-integrity commitments that aim for real results.
- That's Not My Customer
- Teams sometimes discount negative reactions and cling to a few positive comments, which is confirmation bias. Cagan reminds them that qualitative testing is for learning about customers, not for proving the idea right.
- I Don't Care
- Critical feedback is avoided when teams feel no ownership of the problem or don't like the product. Cagan links this to feature teams and Bezos's call for product teams that think like owners.
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.