📖 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 →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
The definitive essay on where good ideas come from: notice problems you personally have, don't force it. Use it as the lens for judging whether your idea is a real problem or a solution in search of one.
From
paulgraham.com
by Paul Graham
~20 min read
- Live in the future and build what's missing.
- The best ideas look like bad ideas at first (schleps and hard-to-explain).
- Start with problems you have, in a domain you actually know.
Open
paulgraham.com →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
The definitive founder essay on why raw ideas are worth very little and why secrecy is the wrong instinct. Graham's argument reframes protection: your real asset isn't the concept but the compounding work of building it, which no NDA can substitute for.
From
paulgraham.com
by Paul Graham
~15 min read
- There's essentially no market for startup ideas, which tells you what they're worth on their own.
- Most startups end up nothing like the initial idea; the value emerges through execution and iteration.
- Treat ideas as questions to explore, not blueprints to guard.
- Develop ideas openly with co-founders and friends rather than locking them away.
Open
paulgraham.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 →
📖 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 →
📄 Article
✓ Link checked
Freemium
Beginner
Why we picked it
Todd Jackson studied how dozens of now-large companies validated their very first idea. The pattern that repeats: deliver the outcome by hand, talk to real users, and watch for genuine emotion. A polite 'that's cool' is a no. Strong reactions are the signal you want.
From
Lenny's Newsletter
by Todd Jackson
~15 min read
- Manual delivery beats a survey for early signal.
- Look for strong emotion, not politeness.
- Great ideas usually start from a problem you have lived.
Open
lennysnewsletter.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Intercom's Jobs-to-be-Done writing shows how to ask what customers are hiring your product to do, which forces you to describe the problem in their words instead of yours. It is practical for teams that are past their first few interviews. A free collection of their best posts on the topic.
From
Intercom
by Des Traynor, Intercom
~short book, free
- Focus on the job, not the customer type
- Describe the problem in the customer's own words
- Features should follow the job, never lead it
Open
intercom.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
A step-by-step guide to running discovery when you have almost no data, aimed squarely at first-time founders. It is practical on finding people to talk to and asking in a way that surfaces truth rather than encouragement. A solid starting point before your first batch of interviews.
From
First Round Review
by Jeanette Mellinger
15 min read
- Start discovery before you have a product.
- Recruit the right people to talk to.
- Ask so customers can safely tell you no.
Open
review.firstround.com →
📖 Book
✓ Link checked
Free
Beginner
Why we picked it
A free, short predecessor to The Right It for when you want the method without buying a book. It lays out cheap experiments (fake buttons, manual concierge, pre-orders) that reveal whether people will act, not just nod. Worth reading before you spend a single rupee on building.
From
pretotyping.org
by Alberto Savoia
~90 pages
- Test the core experience with the smallest possible time and money.
- Watch what people do when asked to commit, not what they say.
- A single well-run experiment can kill or confirm an idea in a day.
Open
pretotyping.org →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
This is the best method for the exact job of learning an industry's language when you cannot yet get face time with people in it. Hoy shows how to lurk in the forums, reviews, and comment threads where your audience already talks, and mine their real words, pains, and workarounds. Do this and you will start speaking the vocabulary before anyone can tell you are new.
From
Stacking the Bricks (Amy Hoy)
by Amy Hoy
video walkthrough
- Find the watering holes where your audience already complains in public
- Collect their exact words, pains, and existing workarounds
- Observation at scale can precede one-on-one interviews
Open
stackingthebricks.com →
📄 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 →
📄 Article
✓ Link checked
India
Free
Intermediate
Why we picked it
Shah argues that to make people switch from what they already use, you need a large jump in perceived efficiency, not a marginal one. In a crowded market that is the bar for your wedge: the incumbent may be good enough for most, so your narrow segment has to feel a dramatic gain. Read it to sanity check whether your improvement is big enough to change behavior.
From
SeedToScale (Accel India)
by Kunal Shah
~10 min read
- People only switch when the efficiency jump is large, not marginal
- Look for inefficiencies incumbents leave in place, not just problems
- A big enough delta makes the new behavior stick and spread
Open
seedtoscale.com →
📄 Article
Free
Intermediate
Why we picked it
Maurya names the exact failure in this question: founders ask what problems their solution can solve instead of what problems customers actually have. A short read on how to flip that and discover the right problem before you commit. Blunt and practical.
From
Love the Problem (Medium)
by Ash Maurya
~8 min read
- Do not start from your solution and reverse into a problem
- The first problems you list are usually the wrong ones
- Discover the problem before you try to validate anything
Open
medium.com →
