How should founders elicit genuine customer pain points during discovery conversations?
4 recorded positions from 3 people, first said Nov 9, 2022. They do not agree — the readings below are what each one actually argued.
Ask indirectly about feelings not directly about the product to surface emotional needs
Hugo Barra · Nov 9, 2022
To uncover emotional needs you must ask indirectly — how they felt, when they last thought about something — and never ask what they think of a product that does X
Dancing around the topic gets customers talking about the underlying feeling instead of evaluating a proposition
26:55 20 Product: Hugo Barra on Lessons Building Hardware Products at Android, Xiaomi, Oculus, and Detect; Feature Kings vs. Budget Kings; 996 Work Culture in China; There Are No MVPs in Hardware; The 3.5-Hour Recruiting Interview
Hugo Barra · Nov 9, 2022
Steve Jobs and Tony Fadell are the product leaders he most admires, and the core lesson from them is that you have to uncover users' emotional requirements, which they will never tell you about directly
Emotional requirements are never volunteered, so you have to find a way in to them
46:07 20 Product: Hugo Barra on Lessons Building Hardware Products at Android, Xiaomi, Oculus, and Detect; Feature Kings vs. Budget Kings; 996 Work Culture in China; There Are No MVPs in Hardware; The 3.5-Hour Recruiting Interview
Also on the record
Gili Raanan · Mar 18, 2024
Asking prospective customers what their biggest pain point or need is yields mostly worthless answers; you must instead offer them something — e.g. framing it as $100M of engineering you will spend on one problem for them — so the power dynamic flips and they focus
When you are doing them a favour rather than asking one, they listen and tell you the real problem they will actually budget for now
25:22 Offer something of value first to flip the power dynamic and surface real pain
Harry Stebbings · Mar 29, 2023 · hedged
Most customer development is poor because people don't ask good questions
8:35 Poor questioning not discovery itself explains most bad customer development
Your assistant can query this graph directly — 4 positions here, 19,646 across the corpus. Add 996.fm over MCP.