Reveal Your Product Blind Spots
summary
Lays out three concrete blind spots—assumptions, biases, and costs—and gives tactics: run an assumption mapping exercise, do continuous discovery, track assumptions in discovery/validate/invalidated columns, and record customer sessions to play clips for stakeholders. Reframe “how hard” as “how much complexity” to expose technical cost, use walking skeleton prototypes and lead scoring for early validation, celebrate invalidation of hypotheses, and prioritize by cost of delay to avoid accumulating tech debt.
AI-written summary · about
chapters (9)
- 0:00Introduction to blind spots
- 1:09Product manager's role explained
- 3:15Assumptions in product development
- 8:13Biases affecting decisions
- 15:16Costs of complexity and delay
- 22:58Best practices to avoid blind spots
- 30:23Q&A on team biases and stakeholders
- 37:07Q&A on long-term product investments
- 38:10Q&A on cultural biases
related talks
29mDriving clarity in ambiguous projects
23mUsing Data to Bridge Product and Engineering Teams
43mHow to Lose Your Feature Overload
44mProduct 101 for Techies and Tech Teams with Amanda Savluchinske
47mStop Building Useless Software
27mRequirements that you didn't know were there
37mHow to Lose Your Feature Bloat?
38mFrom Conversation to Software