The Product Owner’s Guide to Saying No
summary
Core claim: rigorous refusal improves product focus and quality, not endless stakeholder appeasement. Product work relies on definition of done, MoSCoW prioritization and painful trade-offs; teams must manage technical debt (kitchen mess) and use listening plus redirects to say no without burning bridges. Concrete scale: a backlog of 4,500 feature requests, an example product made $1.5M first-year revenue while a needed follow-up had a couple hundred thousand dollar investment and 10x ROI yet stayed deprioritized.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 7:39Making everybody happy
- 9:04How to say no
- 12:22The continuum of easiness
- 14:48Alignment with vision
- 18:04Listening
- 20:27Product Council
- 25:11Conclusion
related talks
41mChallenges of product owner in a new agile team
50mHow to defeat feature gluttony?
57mLearn to Say "No!" Without Being a Jerk
25mOnly one product in the world is completely yours. And why it’s worth losing £10.
16mDear Devs: Your PM Is (Probably) Not Here to Ruin Your Life
16mLessons in Product Leadership
29mWhat 200+ PMs Taught Us About Product Management in Real Life
20mDash Bash