When Trying to Figure Out What Is Worth Building Backfires
summary
A checklist of twelve concrete anti‑patterns that derail product discovery: a two‑axis model of discovery (vision → experiments) versus delivery (roadmap → backlog), examples like Fire Phone lost hundreds of millions and why that failure came from designing for the builder not the buyer, actionable fixes such as engineers doing user research and riding customer support shifts, and warnings about sunk‑cost traps, survivorship bias, proxy selling, rigged validations and pet projects that keep teams building the wrong thing.
AI-written summary · about
chapters (19)
- 0:00Introduction and welcome
- 1:39Fire Phone failure analysis
- 2:20Agile product development model
- 4:26Systemic issues in product development
- 6:55Siloism and miscommunication
- 8:26Taylorism in engineering
- 9:52Resistance to agile methods
- 11:38Pet projects and moral hazard
- 13:05Paperism and hierarchy issues
- 15:13Sales-driven requirements chaos
- 16:18Psychological biases in decision-making
- 18:53Sunk cost fallacy explained
- 20:40Validating solutions with data
- 22:26Survivorship bias in product decisions
- 24:40Psychological distance in user research
- 26:51Summary of anti-patterns
- 28:17Fire Phone case study recap
- 29:28Leadership and product vision
- 30:32Closing remarks and resources
related talks
31mThe 7 Biases of Product Teams
47mThe product confidence trap
27mStrategies for making impossible decisions
29mDriving clarity in ambiguous projects
45mFallacies of Software Development
24mThe Feature Nobody Used & What It Taught Me About Product Engineering
39mUno! Winning at product discovery
38mFallacies of Software Development