✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
This is the sharpest short framework for the exact question: is the problem a nice-to-have (vitamin) or something people are actively hurting from (painkiller). Rhea's most useful test is a gut check on your own interviews, if you find yourself convincing a prospect they have a problem, or getting excited every time you catch a glimpse of it, that is a warning sign you have a vitamin. It reframes the judgment from what you hope is true to what customers already feel without you nudging them.
From
brianrhea.com
by Brian Rhea
About a 7 minute read
- Painkillers get bought without reminders because the pain is already felt; vitamins get put off because the need is theoretical and non-urgent.
- If you are talking a prospect into believing they have the problem during an interview, you are probably looking at a vitamin, real pain shows up on its own.
- Find the pain first through honest customer conversations, then design the fix, not the other way around.
Open
brianrhea.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
Judging whether people will actually change their behavior comes down to how well you can hear intensity in what they say, and this is the most practical book on doing exactly that. Hansen, a bootstrapped SaaS founder, walks through the specific questions and listening moves that get past polite answers to the real emotional weight behind a stated problem. It is the how-to that makes the vitamin versus painkiller judgment something you can actually do in a live conversation instead of guessing.
From
deployempathy.com
by Michele Hansen
Full book, roughly 250 pages
- Ask about the last time someone hit the problem and what they did about it; workarounds and effort reveal true intensity better than a rating of how much it bothers them.
- People soften and rationalize their pain, so listen for emotion, hesitation, and the stuff they already spend money or time on to cope.
- Behavior in the past is the honest signal, if they never built a workaround or paid to escape it, the problem is likely a nice-to-have.
Open
deployempathy.com →
📖 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 →
📄 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 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
Steve Blank's argument for searching for a business model before building one, the get out of the building philosophy in short form. It contrasts the old write a plan and build in secret approach with testing hypotheses on real customers. A crisp, credible piece to send anyone who thinks planning can substitute for talking to people.
From
Harvard Business Review
by Steve Blank
15 min read
- No business plan survives first contact with customers.
- Get out of the building and test your assumptions with real buyers.
- Favor experiments and customer feedback over elaborate up front plans.
Open
hbr.org →
📖 Book
✓ Link checked
Paid
Advanced
Why we picked it
The book that coined get out of the building and launched the customer development movement. Blank's core claim is that a startup searches for a business model rather than executes one, so your early job is to test hypotheses against real customers before you scale anything. It is heavier than The Mom Test, but it gives you the full framework for validating a market before you build for it.
From
Wiley
by Steve Blank
- Startups search for a business model, they do not just execute a plan
- Test your riskiest assumptions with real customers before committing to build
- Customer discovery and validation come before you spend on customer creation
Open
wiley.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Blank's own blog distills the argument from his book into a short, free read: most startups don't fail on execution, they fail because nobody confirmed a real customer had a real problem first. It is a faster on ramp than the book if you want the philosophy before committing to the full process. Good to read alongside the HBR piece for the free version of the same core idea.
From
steveblank.com
by Steve Blank
- Product development and customer development are two separate tracks needing separate processes.
- Most startup failure is a sales and marketing failure, not a product failure.
- Get hypotheses in front of real prospects early, revise them, repeat.
Open
steveblank.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Amy Hoy and Alex Hillman built the Sales Safari methodology, and a business, around finding what an audience already complains about paying to fix, then selling before building. This piece, written by Hillman, updates that research method for modern community platforms, which is a useful complement to one-on-one interviews when you want pattern evidence across many potential customers at once.
From
Stacking the Bricks
by Alex Hillman
12 min read
- Look for what people are already frustrated enough about to have spent money trying to fix.
- Research an audience's own words in public forums before you ever pitch them anything.
- Pre-selling forces you to describe a specific, paid outcome before you have built the thing that delivers it.
Open
shorts.stackingthebricks.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
Freemium
Intermediate
Why we picked it
If you are selling to companies rather than consumers, this is the specific playbook. Four concrete ways founders got signal before building, from doing the job by hand for one customer to interviewing dozens of potential users first.
From
Lenny's Newsletter
by Lenny Rachitsky
~12 min read
- Do the job by hand for one real customer before automating.
- Interview a wide set of potential users before committing.
- B2B signal looks different from consumer signal.
Open
lennysnewsletter.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
This is the canonical piece that put jobs to be done on the map, written by the people who coined it. It uses the famous milkshake story to show that customers do not buy products, they hire them to make progress in a specific situation, which is the exact lens this question is about. Read it as the clearest short starting point before going deeper into JTBD.
From
Harvard Business Review
by Clayton Christensen et al.
~20 min read
- Customers hire a product to make progress in a specific circumstance, so the job, not the customer profile, is the unit of analysis.
- The same product can be hired for very different jobs, which changes how you build and market it.
- You find the job by studying the struggle and the context, not by asking people to rank features.
Open
hbr.org →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
A pre-seed fund's practical checklist for what real validation looks like before you write code, insisting on quantified answers, like 87 percent said they'd use this twice a week, over vague enthusiasm. It walks through using existing online communities to find and talk to prospects before you have anything to show them. A good gut check if your current evidence is a handful of that sounds cool reactions.
From
Hustle Fund (Hustle Commons)
- Quantify responses, most people liked it is not evidence of anything.
- Ask how often and how much they'd pay, not whether they like the idea.
- Find prospects in existing online communities before you build anything to show them.
Open
hustlecommons.com →
🧵 Thread
✓ Link checked
Free
Intermediate
Why we picked it
A long comment thread of founders and operators arguing through the vitamin versus painkiller framing with their own real examples and counterexamples, including honest pushback that plenty of vitamins, like coffee, do fine commercially anyway. It is a useful antidote to treating the metaphor as a rigid rule rather than a rough heuristic. Read the top comments for the nuance a short essay would flatten.
From
Hacker News
- The vitamin versus painkiller split is a heuristic, not a guarantee of success or failure.
- Some genuine vitamins, habitual or pleasurable products, build huge businesses anyway.
- Real founders' counterexamples are more useful here than the clean version of the rule.
Open
news.ycombinator.com →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
Built around the well known CB Insights statistic, this piece is refreshingly concrete about what evidence to look for, an existing ugly workaround, like a spreadsheet, a Slack hack, or extra headcount, as the tell that a problem is real. It gives you interview count benchmarks too, so you know roughly when you've talked to enough people to trust the pattern. A quick, practical read before you draft your interview list.
From
The VC Lens
by Sayanee Bhowmik
- If there's no existing workaround at all, be suspicious that the problem is real.
- You're usually done interviewing when you hear confirmation more than surprises.
- Ten to twenty well chosen conversations tend to reveal the major patterns.
Open
vclens.substack.com →
Why we picked it
A short, practical field guide to customer discovery: who to talk to, how to find them, and how many. Pairs perfectly with The Mom Test, Fitzpatrick teaches the questions, Constable teaches the logistics.
From
talkingtohumans.com
by Giff Constable
~80 pages (free PDF available)
- Decide who you need to learn from before you start.
- Recruiting interviewees is a skill, scripts and channels included.
- Get out of the building; patterns emerge faster than you expect.
Open
talkingtohumans.com →
Why we picked it
The book that gave the world 'MVP', 'build-measure-learn', and 'validated learning'. It reframes a startup as a series of experiments, not a bet, the mental model everything else in this category builds on.
From
theleanstartup.com
by Eric Ries
~330 pages
- Progress = validated learning, not features shipped.
- Build the minimum that produces a real learning loop.
- Decide pivot-or-persevere on evidence, on a schedule.
Open
theleanstartup.com →
📄 Article
India
Free
Beginner
Why we picked it
A roundup of concrete advice from Indian investors and mentors, and the standout point for this question is direct: founders usually pitch a list of features when asked what they've built, instead of naming the problem and the evidence that it's real. It is grounded in the kind of pitch conversations that happen constantly in Indian accelerator and mentor settings. A quick read to sanity check how you're currently describing your own idea.
From
YourStory
- If you're listing features instead of naming a problem, you likely haven't validated it yet.
- Narrowing to one specific customer segment surfaces real pain faster than targeting everyone.
- Mentors consistently see founders skip straight to solutions without naming who hurts and why.
Open
yourstory.com →
