Continuous Discovery Habits by Teresa Torres: People’s Stories That Translate into Opportunity Mapping — Key Points from Chapters 5 and 6

Niloy T. — Unsplash

Introduction

This article follows on from the previous ones:

1 — Continuous Discovery Habits by Teresa Torres: What It Really Means to Discover Products — Key Points from Chapters 1 and 2 2 — Continuous Discovery Habits by Teresa Torres: Where Business and User Behavior Intersect — Key Points from Chapters 3 and 4

It once again reflects my key insights from reading Continuous Discovery Habits by Teresa Torres. This time, we enter the phase where the Product Trio steps out of its bubble of assumptions and begins validating them (or not) with customers.

If the previous chapters focused on defining outcomes and mapping what we think we know, Chapters 5 and 6 teach us how to listen to customers’ pain points, motivations, frustrations, and expectations — and how to “turn that soup of data” into strategically structured information.

This is an important phase, yet one that is often neglected in most organizations.

Deepening People’s Stories Through Interviews

The main lesson from Chapter 5 is that humans are terrible at describing what they did, predicting their own behavior, or articulating their needs in an abstract way. In Portuguese, we have sayings that reflect this well: 1 — “Do as I say, not as I do” 2 — “Every storyteller adds something to the story”

It’s hard for us to answer questions like: “What do you need?” Usually, the answer is either completely off or we say we don’t need anything. When we ask customers this question in a product context, what they often give us is a solution (a potential feature) — frequently biased by what they think we want to hear.

Teresa Torres suggests that the focus of our weekly interviews should be stories. Instead of heavy planning or rigid scripts, we should avoid hypothetical questions and instead anchor users in specific past moments: “Tell me about the last time…” From there, we unravel the thread — it’s our responsibility to unpack that data.

Practical Example at MediFlow

Instead of asking a clinic administrator, “Would you like an SMS button for billing?”, we can reframe the question as: “Can you tell me about the last time a patient left the clinic without paying? Can you describe what happened?”

Within that story, we can uncover whether the issue was patient forgetfulness, administrative pressure, or a failure in the payment system.

The goal here is to initiate part of the co-creation process — this time directly with the customer. Together, we explore the context to identify pain points, motivations, frustrations, expectations, and needs — what Teresa calls Opportunities.

Taming the Chaos: Mapping the Opportunity Space

In Chapter 6, we learn how to deal with the “mess” that interviews generate. After hearing multiple stories, the Trio ends up with a long list of problems. But how do we prioritize what to work on?

The answer lies in what Teresa Torres calls the Opportunity Solution Tree (OST).

Opportunities are not just “problems to solve”; they are gaps in the market where we can create value. The golden rule is never to accept a solution disguised as an opportunity — as we saw earlier.

For example: If a customer says, “I need an Excel report,” they are giving us a solution. What they really need might be: “I need to share billing data with my accountant quickly.”

The OST structure helps us organize opportunities into parent-child relationships, ensuring that:

1. We work on one opportunity at a time, limiting the team’s Work in Progress (WIP).
2. Each opportunity is distinct, avoiding overlaps that lead to indecision.
3. We focus on impact, evaluating which opportunity — if solved — brings us closer to our Product Outcome.

Example of an Opportunity Solution Tree for MediFlow

Outcome: Reduce the average time it takes clinics to receive payments by 20%

Opportunity Space:

• Patients forget to pay after leaving the consultation
• Patients leave in a hurry to avoid reception queues
• The manual billing process is inefficient and stressful
• Administrative staff fear in-person conflict or even calling patients to collect payments
• Payment methods are limited (physical/local)
• Patients want to pay digitally or remotely

Solutions:

• Automatic payment via Apple Pay / Google Pay
• Payment links sent via SMS
• AI (Innovation): An AI agent (chatbot) for automated debt negotiation, reducing emotional burden on administrative staff
• AI (Innovation): A predictive model to identify patients at higher risk of delayed payment and send SMS notifications

Conclusion

One of the core habits of Continuous Discovery is conducting interviews (customer touchpoints and data collection) at least once a week. These touchpoints — especially when building a new product — are not meant to validate ideas, but to discover new opportunities every week.

The results of these interviews (what we might call data, which should later become strategic information) should be synthesized immediately — for example, using what Teresa Torres calls Interview Snapshots. This allows us to capture the essence of each conversation as soon as it ends, preventing us from forgetting key findings and struggling to turn them into insights.

Finally, we must remember that an OST is a living artifact — just like any real tree. Reviewing it every 3–4 interviews, as the Trio gains more knowledge, is essential.

This article is part of my shared reading journey of Continuous Discovery Habits by Teresa Torres. The next article will cover Chapters 7 and 8.