Product discovery focuses on deciding what to build, moving beyond the agile focus of simply building software efficiently.
A high percentage of well-intentioned product ideas fail to create a positive impact, with some even worsening the customer experience.
Successful products must mitigate value, usability, feasibility, and business viability risks to avoid building something customers don't want or can't use.
Dan Olson's pyramid model illustrates how to achieve product-market fit by systematically connecting a target customer's needs to a specific feature set.
Engineers provide essential technical perspective and contribute more than just code, making them vital partners in the discovery process.
Personas help teams avoid building for everyone by creating a specific, detailed representation of the target user, guiding feature decisions.
Applying Maslow's hierarchy of needs helps prioritize foundational user requirements, ensuring basic needs are met before adding advanced features.
The Jobs to be Done (JTBD) framework reframes product value by focusing on the functional and emotional "job" a customer hires a product to do.
The Value Proposition Canvas is a tool for systematically mapping customer pains and gains to product features that relieve pain and create value.
The Kano Model helps prioritize development by categorizing features as baseline, performance, or delighters, focusing on maximizing user satisfaction.
Product discovery is not a one-time phase but an ongoing process of forming and testing hypotheses through continuous customer interaction.
28:39Maria Daniela Lica
39:27Kaya Sohyun Kim
28:39Eleftheria Batsou
23:03Robert Hoffmann
26:13Malte Breitzmann & Saskia Henatsch
57:45Robert Hoffmann & Christian Denich
23:44Richard Bown
24:07Szymon Chmal
.webp?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
Tabit GmbH