Product Talk · Starting Up

📖 Book

✓ Link checked Paid Intermediate

Why we picked it The standard modern playbook for keeping discovery continuous so roadmap decisions stay grounded in real customer input, not one-off research. Exactly what founders need to stay close to users while shipping.

Continuous Discovery Habits

From Product Talk by Teresa Torres ~240 pages

Start from a clear desired outcome.
Interview customers weekly to surface opportunities.
Use an opportunity solution tree to visualize and align your decisions.

Open producttalk.org →

Answers How do I build a roadmap without over-planning? How do I keep talking to users while I'm heads-down building? How do I say no to feature requests without losing customers?

✍️ Essay

✓ Link checked Free Beginner

Why we picked it Torres lays out a clean ladder for testing willingness to pay without waiting to finish the product: ask about past spending, then run a demand test with a real pricing page, then actually ask for the money via pre-orders or a concierge sale. It is practical and honest about why hypothetical 'would you pay?' questions give you data you cannot trust. Useful whether you are in Bengaluru or building outside the big startup hubs, since none of it needs a finished product.

Ask Teresa: How Can You Test a Customer's Willingness to Pay?

From Product Talk by Teresa Torres ~10 min read

Start from behaviour: what people already subscribe to or pay for beats any answer to a hypothetical price question.
A mock pricing page plus a waitlist or checkout click is a cheap demand test you can run before you build.
The strongest test is simply asking people to buy now (pre-order, Kickstarter, or a hand-run concierge sale) and seeing who pulls out a card.

Open producttalk.org →

Answers How do I test whether people will actually pay, not just say they like it? My ideal customer can't afford my product. Did I define them wrong?

📖 Book

✓ Link checked Freemium Intermediate

Why we picked it When 20 interviews each surface a slightly different problem, the fix is not more interviews, it is a structure to sort them. Teresa Torres's opportunity solution tree gives you exactly that: a way to map every pain point you heard against one desired outcome, so real, recurring opportunities separate themselves from one-off noise. This guide is the clearest free explanation of the method, and it points to the full book if you want to go deeper.

Continuous Discovery Habits: Discover Products that Create Customer Value and Business Value

From Product Talk by Teresa Torres ~10 min read (companion to a full book)

Group each interview finding as an opportunity (a customer need, pain, or desire) and place it under a single desired outcome, so patterns become visible instead of a flat list of quotes.
A problem that keeps recurring across interviews earns a spot on the tree, a one-off mention does not, which is a concrete rule for pattern versus noise.
The tree is meant to keep changing as you keep talking to customers, so treat your 20 interviews as a starting point, not a finished map.

Open producttalk.org →

Answers I've done 20 interviews and every person described a slightly different problem. How do I know if there's a real pattern or just noise?

📄 Article

✓ Link checked Free Intermediate

Why we picked it The thing that drains most founders is treating research as a big occasional project, so it always feels heavy. Teresa Torres makes the opposite case: one small, regular touchpoint with users each week becomes a keystone habit that quietly pulls the rest of your discovery along with it. For a solo founder, this is the mindset shift from dreading research to running it as a light, repeatable routine instead of a weekly ordeal.

This Keystone Habit Will Fuel the Rest of Your Continuous Discovery Habits

From Product Talk by Teresa Torres About a 10 minute read

A small weekly customer touchpoint compounds: once it is a habit, prototyping and testing start happening more naturally too.
Frequency beats depth: short, regular conversations keep you learning continuously instead of front-loading one exhausting research sprint.
Automate the boring part (recruiting) so the habit survives the weeks you feel busy or low on energy.

Open producttalk.org →

Answers As a solo technical founder who hates sales calls, how do I do user research without it draining me every week?

✍️ Essay

✓ Link checked Free Intermediate

Why we picked it The strongest way to research a private competitor is to talk to the people who left them, and this essay grounds that tactic in a real interview method. Teresa Torres explains the story-based approach, where you collect the customer's actual story of what happened rather than asking leading questions, and she names churned users as a segment worth interviewing to learn what the real problem was. It turns a vague idea (go talk to their ex-customers) into a repeatable habit you can run every week.

Ask Teresa: How Do You Select Customers for Customer Interviews?

From Product Talk by Teresa Torres About a 12 minute read

Interview people who churned from a competitor: they tell you the real friction and gaps that no public number would.
Use story-based interviewing, spend the time collecting what actually happened, not pitching your own product or asking hypothetical questions.
Deliberately vary who you talk to (power users, first-timers, disengaged, churned) so you are not just hearing one slice of the story.

Open producttalk.org →

Answers How do I do competitive research when my competitors are private and share almost no public numbers?

📄 Article

✓ Link checked Free Beginner

Why we picked it Torres takes the next step after you accept you cannot reach significance: figure out what you are actually trying to learn, then pick a method that fits. She walks through swapping A/B tests for customer interviews, paper prototypes, think-aloud sessions, and competitive research depending on the question, so low traffic stops being a dead end. The line to carry: do not let a lack of traffic keep you from learning what you need to learn.

What to Do When You Don't Have Enough Traffic to A/B Test

From Product Talk by Teresa Torres

Match the method to the question: value and desirability questions are better answered by talking to users than by an underpowered test.
Interviews, paper prototypes, and think-aloud usability sessions give directional signal without needing statistical power.
You can also buy temporary traffic (paid search) to a page if you genuinely need a quantitative read.

Open producttalk.org →

Answers How do I run a growth experiment properly when my user numbers are too small for statistical significance?