📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
The single best thing ever written on customer conversations. It teaches you to ask about the customer's life and past behaviour, not your idea, so you can't be lied to. If a founder reads one thing before talking to a single customer, it's this.
From
momtestbook.com
by Rob Fitzpatrick
~130 pages
- Talk about their life, not your idea.
- Ask about specifics in the past, not opinions about the future.
- 'That's so cool, I'd totally buy it' is a compliment, not data, dig for commitment and evidence.
Open
momtestbook.com →
📖 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.
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 →
📖 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.
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 →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
The original, primary source where the RICE framework was introduced, cite this, not the SEO reposts. The clearest way to compare hard-to-compare feature ideas.
From
Intercom Blog
by Sean McBride
~12 min read
- Score = (Reach x Impact x Confidence) / Effort.
- Forces you to quantify confidence and expose low-confidence pet projects.
- Comparable scores let you rank features objectively.
Open
intercom.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
The canonical PM-community reference on choosing what to build next, from the most-read product newsletter. A pragmatic overview of scoring frameworks and how to actually use them.
From
Lenny's Newsletter
by Lenny Rachitsky
~15 min read
- Prioritize around outcomes, not output.
- Use scoring frameworks (RICE/DRICE) to compare ideas objectively.
- Deeper investigation kills 'promising' bets and elevates quiet high-ROI winners.
Open
lennysnewsletter.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
The primary-source telling of the milkshake story, the single most memorable illustration of Jobs to Be Done, straight from Christensen and HBS. The best on-ramp to JTBD.
From
HBS Working Knowledge
by Clayton Christensen (via Harvard Business School)
~8 min read
- Customers 'hire' products to do a job in a specific situation
- The milkshake was hired to make a boring commute bearable, not just for taste
- Understand the job, and the right product improvements become obvious
- Demographics miss the point, situation and job drive purchases
Open
library.hbs.edu →
✍️ Essay
✓ Link checked
Free
Advanced
Why we picked it
Cagan argues your job is to deliver outcomes, not to maintain a prioritized list of everyone's requests. That is the backbone of anchoring a no to the outcome you are chasing rather than to who shouted loudest. Read it to stop treating your roadmap as a request queue.
From
Silicon Valley Product Group (Marty Cagan)
by Marty Cagan
10 min read
- Commit to problems and outcomes, not a fixed list of features
- A request spreadsheet quietly pushes in things users do not actually need
- Frame the roadmap around the outcome so a no has a reason behind it
Open
svpg.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
The full book behind the essay, for when you want the system and not just the idea. It gives you the language of outcomes over outputs so you can defend a no to your team and your customers with something concrete. Worth it if requests are piling up faster than you can reason about them.
From
Melissa Perri (O'Reilly)
by Melissa Perri
200 pages
- Tie every build decision to a measurable customer or business outcome
- Say no to work that only adds output without moving an outcome
- Set up the org so outcomes, not feature counts, decide priority
Open
amazon.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Turns the vague feeling of product-market fit into a number you can move. Ask users how they would feel if they could no longer use the product, then track the share who say 'very disappointed'. Under 40 percent means keep working. A test you can run on an idea long before you scale it.
From
First Round Review
by Rahul Vohra
~20 min read
- The 40 percent 'very disappointed' benchmark for product-market fit.
- Segment to your high-expectation customers and build for them.
- Make the fit score a metric you improve quarter by quarter.
Open
review.firstround.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
A hands on walkthrough of the unglamorous middle step, putting every piece of feedback in one place, tagging it, and rolling it up into themes. This is literally how you get from twenty scattered requests to three counted problems. Read it when you need a repeatable process, not just a philosophy.
From
Intercom
- Centralize feedback with the customer context attached.
- Tag by theme so volume becomes a countable signal.
- Let the themes, not the loudest voice, shape the roadmap.
Open
intercom.com →
📖 Book
✓ Link checked
Free
Intermediate
Why we picked it
Basecamp's battle-tested, opinionated system for shipping meaningful work in fixed cycles without endless backlogs, a primary source, free in full. The antidote to over-planning your roadmap.
From
Basecamp / 37signals
by Ryan Singer
free online book
- Work in short cycles with a cool-down between them.
- Fix time, vary scope, use 'appetites,' not estimates.
- Make bets, not plans; no runaway backlog.
Open
basecamp.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Traynor describes finding fit by looking for clusters of demand, groups of customers pulling for the same underlying thing, rather than chasing individual asks. It is the clearest statement of your core move, cluster by problem and build for the biggest, most painful cluster. Short and directly on point.
From
Underscore VC
by Des Traynor
- Look for clusters of demand, not one off requests.
- A strong cluster is many customers pulling in one direction.
- Build for the cluster that is both large and underserved.
Open
underscore.vc →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
The cleanest distillation of the one framework that turns a customer chat into a relationship instead of a survey. The three rules (talk about their life not your idea, ask about the past not hypotheticals, and chase real commitments of time, reputation, or money) are exactly how you get an early customer to tell you what nearly stopped them from buying and who else you should talk to. Rekhi is a product leader, so the examples are operator-grade, not book-report fluff.
From
Sachin Rekhi's Blog
by Sachin Rekhi
10 min read
- Never pitch your idea in the conversation; ask how they handle the problem today and what it costs them, so praise can't lie to you.
- The strongest signal is a commitment that costs them something: a trial, an intro to a colleague, or a pre-order.
- 'Would you buy this?' teaches you nothing; 'walk me through the last time you dealt with this' surfaces the real story and the referral.
Open
sachinrekhi.com →
📖 Book
✓ Link checked
Paid
Advanced
Why we picked it
Gilad's work is about ranking ideas by the strength of the evidence behind them, not by who shouted loudest. His Confidence Meter gives you a way to discount a single anecdote and weight a validated pattern, which is exactly the discipline messy feedback needs. Useful when you have several plausible problems and must choose.
From
itamargilad.com
by Itamar Gilad
- Weight ideas by evidence quality, not opinion or seniority.
- One customer's request is weak evidence on its own.
- Cheap tests raise confidence before you commit to building.
Open
itamargilad.com →