📖 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
Intermediate
Why we picked it
If your idea feels unglamorous or annoyingly hard, this essay explains why that can be a good sign rather than a reason to drop it. Graham shows how founders unconsciously avoid tedious, painful problems, which is exactly why those problems stay unsolved and valuable (Stripe is his example). Read it to check whether you are dismissing a strong idea just because the work looks like a slog.
From
paulgraham.com
by Paul Graham
about 10 min read
- The hardest, most tedious problems are often the most valuable and least crowded
- You may be blind to good ideas because your mind avoids the schlep
- A company is defined by the difficult work it is willing to take on
Open
paulgraham.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Steve Blank coined get out of the building, and this is a clean primer on why talking to customers is a search for facts your building cannot give you. It frames customer discovery as testing your assumptions against real people rather than defending a plan. A short, foundational read on why you are doing this at all.
From
Kauffman Entrepreneurs (Steve Blank)
by Steve Blank
10 min read
- Facts about your customers live outside the building, go find them
- Treat your idea as a set of hypotheses to test, not a plan to defend
- Customer discovery is a search, expect several iterations before it clicks
Open
entrepreneurship.org →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
This is the most concrete method we found for collecting the complaints nobody has fixed when you cannot yet get people on calls. You go to the forums, reviews, and support threads where a trade already gathers and log their pains, workarounds, and the exact words they use. It is a practical way to earn context on an unfamiliar industry from the outside before you ever build anything.
From
Solving Product (Amy Hoy and Alex Hillman method)
by Étienne Garbugli
Medium read
- Find the watering holes where a trade already complains online
- Log pains, workarounds, and the exact words people use
- Problems already exist in the open, you just have to listen for them
Open
solvingproduct.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Entering an unfamiliar industry means you cannot see the walls and dead ends that veterans already know. Dixon explains that a good founder holds a map of who tried this before, what happened, and why, and that this map is what real domain knowledge looks like. It gives you a concrete goal for your research: build the maze map through history, analogy, and direct experience.
From
cdixon.org
by Chris Dixon
short read
- Value is in the map of the terrain, not the spark of the idea
- Learn the maze through history, analogy, theory, and direct experience
- Knowing who already failed at this and why is domain knowledge
Open
cdixon.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
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 →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
Lenny interviewed founders of Gong, Notion, Figma, Amplitude, Retool and more to trace where their idea actually came from. The surprising finding is that most founders had no special background in the space and spoke to around thirty potential customers before committing. Read it to see that ideas come from paying attention, not from a rare gift.
From
Lenny's Newsletter
by Lenny Rachitsky
About 15 min read
- Most founders lacked deep prior expertise in their problem space
- Ideas came from noticing something, then validating with many conversations
- A median of about thirty customer chats preceded real commitment
Open
lennysnewsletter.com →
📄 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
India
Freemium
Beginner
Why we picked it
Zerodha built one of India's most used products with a tiny team and a stubborn focus on simplicity over polish. Kamath's view that complexity is a bug backs up the idea that you need clear thinking, not heavy design. A grounded Indian example of how much (and how little) design a founder really needs.
From
Inc42
by Inc42
15 minute read
- Radical simplicity beats feature-heavy, over-designed products
- A small team can build a category leader by keeping it clear
- Clarity of thought matters more than visual sophistication
Open
inc42.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
This is the honest counterweight to the romance of the naive disruptor, and it maps onto your short answer directly. It shows outsiders do bring fresh ideas but often struggle to make them land without enough context, so the edge only pays off once you close the gap. Read it to keep your fresh eyes without deceiving yourself that inexperience alone is an advantage.
From
Kellogg Insight, Northwestern
by Kellogg Insight
Medium read
- Fresh outsider ideas are real but harder to execute without context
- Deep expertise can cause fixedness, yet some knowledge is required
- Combine fresh perspective with enough learning to be taken seriously
Open
insight.kellogg.northwestern.edu →
