How to fix a failed discovery
summary
A single corrective claim: include a product or technical product manager in discovery because without one milestones go wrong. Case evidence: a built streaming API wasted two years when customers proved non‑adopters; a well‑documented vision fails after confirmation‑biased interviews reveal customers already use an alternative; undocumented scope causes scope creep and low morale. Practical fixes are concrete: ask why and quantify value, run interviews, produce architecture, roadmap, epics, and use thin slices and feedback cycles to reduce risk.
AI-written summary · about
chapters (5)
related talks
29mWhat 200+ PMs Taught Us About Product Management in Real Life
44mPressing questions in Product Management
01h 00m3 Key Questions For Products Teams To Answer
26mTake a step back
15m⚡️ FEDC 2018 - Rob Harr
39mProduct Oops: Common mistakes in Product Operations
37mA 3-step process for building better products
31mHow Exceptional Product Managers discover unmet customer needs