Reading path · 3 pieces · About 36 min
Are you learning what customers need—or collecting requests?
Recognize the feature-request trap, observe a real product journey, then organize customer evidence around an outcome. The final guide is the longest reading: pause before it if you want to split the route into two sessions.
Who this is for: Product teams whose backlog grows faster than their understanding of customers.
Take away: A customer question and a small opportunity to investigate before choosing a solution.
Start reading ↓Estimates use 250 words per minute, rounded up for each piece. Allow extra time for the reflection at the end. Open a piece for its selection note and available summary, then continue to the original.
01 / Break the request loop
Andrew Chen explains how asking engaged users for missing features can distract from the real reason others leave. Start by questioning whether more product is the answer at all.
Pause here: Which explanation for weak usage would not require another feature?
02 / Observe a real journey
Stripe’s friction-log practice records context, expectations and moments of difficulty, then follows feedback through to changes. Treat it as a situated observation, not representative customer research.
Pause here: Whose experience does your observation describe, and whose does it leave out?
03 / Map evidence before solutions
Teresa Torres connects outcomes, customer opportunities, solutions and assumption tests. Pay particular attention to the prerequisites: customer context and story-based interviews, not a workshop full of invented needs.
Pause here: Do you have customer evidence for this opportunity, or only a plausible story?
Chen warns against treating more features as the default cure for weak usage. Stripe’s friction logs make a specific experience visible, but an employee’s experience is not proof of what a whole customer segment needs. Torres provides the missing step: use story-based interviews to understand opportunities before mapping and testing solutions. The methods complement one another only if you keep observations, interpretations and customer evidence separate. A polished tree built from guesses is still a guess.
Digna Legi synthesis of the linked readings, not a claim that the authors endorse this combined approach.
Put five minutes aside
Use paper or your own notes app. These prompts are Digna Legi’s exercise, drawn from the readings.
Before you leave: Which feature request will you turn into a past-behavior interview question before choosing a solution?
Allow Google Analytics to measure visits and reading-link clicks using cookies. Optional; the site works without it. Privacy details