📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
When you feel that something is broken but cannot name it, Christensen's Jobs-to-be-Done lens gives you a way to describe the actual progress a person is trying to make in a specific situation. That reframing turns a fuzzy hunch into a concrete job you can go test with real people, which is exactly the move from vague to sharp. It is the canonical text on the idea, and it is a starting point for thinking in jobs, not a formula to follow blindly.
From
HarperBusiness
by Clayton M. Christensen, Taddy Hall, Karen Dillon, David S. Duncan
~288 pages
- People do not buy products, they hire them to make progress in a specific circumstance, so define the job, not the demographic.
- A job has functional, social, and emotional dimensions, which is often where the real, unmet problem is hiding.
- Once you can state the job clearly, you have a testable claim you can validate or kill by talking to the people who have it.
Open
amazon.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 →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
The origin text for the modern MVP and validated-learning vocabulary every founder now uses. Read it for the mental model that a startup is a series of experiments, not a single bet.
From
theleanstartup.com
by Eric Ries
~330 pages
- Progress = validated learning, not features shipped.
- Run the Build-Measure-Learn loop as fast as you can.
- An MVP is a learning tool, not a cheap product.
Open
theleanstartup.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
Hall's book gives you the research discipline behind good interviewing: how to avoid leading a witness, how to write a discussion guide, and how to separate what you observed from what you interpreted. It's aimed at product teams generally, so it's broader than customer development books, but the interviewing chapters translate directly to founder conversations. It's a fast read and cuts the fluff other research books carry.
From
A Book Apart / Erika Hall
by Erika Hall
~120 pages
- Write your questions down in advance, improvising under pressure tends to lead the witness.
- Separate your notes into said, did, and your interpretation, don't blend them.
- A clear purpose statement and informed consent make people more honest, not less.
Open
abookapart.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
This is the clearest playbook for show, don't ask. The five day structure ends with a rough, facade-level prototype in front of five real people on Friday, and you watch their face and hands rather than asking leading questions. Useful even if you compress it to two or three days for a solo founder.
From
Jake Knapp, John Zeratsky, Braden Kowitz
by Jake Knapp
~280 pages
- Build a facade prototype, just realistic enough to react to, not a working product.
- Interview one person at a time and let them think out loud while using it, resist jumping in to explain.
- Confusion and hesitation on their face is more honest data than anything they will tell you afterward.
Open
thesprintbook.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Blank invented customer development, and this manifesto boils it into a short set of rules, starting with the idea that there are no facts inside your building so get outside. It is the origin of the discipline that says a startup is a search for a business model you must test, not execute. Read it for the founding principles in one page.
From
Steve Blank
by Steve Blank
12 min read
- There are no facts inside the building, so get out and talk to customers
- A startup searches for a business model, it does not just execute a plan
- Your assumptions are hypotheses until customer evidence confirms them
Open
steveblank.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
To say no to the right requests you need feedback you can trust, and this shows how to get it by watching customers rather than just taking their asks. It reinforces that observing the struggle tells you more than the feature name they hand you. Practical field technique for separating a stated want from a real need.
From
First Round Review
by Michael Sippey
12 min read
- Watch what customers do, not only what they ask for
- Get close to the actual struggle to find the real problem
- Stated requests are a starting point for questions, not a spec
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 →
📖 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 →
✍️ Essay
✓ Link checked
Freemium
Intermediate
Why we picked it
This is the original milkshake essay: researchers sat in a parking lot and watched who bought milkshakes and when, instead of asking customers what flavor they preferred, and found the real job was keeping a bored commuter's one free hand busy. It is the founding case study for researching the job someone is hiring a product to do rather than their stated preferences.
From
Harvard Business Review
by Clayton Christensen, Scott Cook, Taddy Hall
~20 min read
- Segment by the job a customer is trying to get done, not by their age, income, or stated preferences.
- Direct observation of purchase moments revealed a job no survey had ever surfaced.
- A product that nails the real job can outsell a technically superior competitor that answers the wrong question.
Open
hbr.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
Drew Houston did not build Dropbox before testing demand, he filmed a video showing how it would work and posted it to Hacker News, turning a 5,000 person waitlist into 75,000 overnight. This is the clearest example of validating a product nobody had used yet without writing production code.
From
Shortform
by Shortform
~10 min read
- A short video showing the product in use can validate demand before a single line of code is written.
- Seed the demo where your actual target audience already spends time, tailored to that community.
- Watch signup and share behavior, not just comments, as the real signal of interest.
Open
shortform.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Before building any shoe inventory or logistics, Nick Swinmurn photographed shoes from local stores, posted them online, and manually bought and shipped whatever sold. It shows how to test a completely new behavior (buying shoes sight unseen) by faking the back end and watching real purchase decisions, not opinions.
From
What Is MVP
by What Is MVP
~10 min read
- Fake the operations behind a new offering so customers experience it as real while you learn cheaply.
- Real purchase behavior, even at a loss, is a far stronger signal than a survey saying yes.
- Let the ugly, manual, unprofitable version run long enough to see if demand is real before you scale it.
Open
whatismvp.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
The canonical fake-door test, told by the founder who ran it. Buffer started as a two-page site: one page pitched the tool, a pricing button led to an email capture, and every signup got a personal note. Real demand, real conversations, a paying customer in weeks, and not a line of product code.
From
Buffer
by Joel Gascoigne
~10 min read
- Test willingness to pay with a pricing page before you build.
- Email every signup by hand and start a conversation.
- A landing page measures behaviour, not opinions.
Open
buffer.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
A practical walkthrough of building only the button or menu item for a feature that does not exist yet, then measuring who clicks it, as the fastest way to see whether a struggle is real enough for people to reach for a solution. Good for testing one specific idea inside something you have already partly built.
From
Amplitude
by Amplitude
~10 min read
- Build only the entry point (button, link, pricing tier) for a feature, not the feature itself.
- Clicks measure real intent to solve the problem, which surveys and interviews cannot fully capture.
- Always tell people what happened after they click, an honest waitlist message beats a dead end.
Open
amplitude.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
GV's method for building a realistic facade and testing it with five target customers in a single week, which is the interview flavoured cousin of the fake door. Their fake it philosophy, a convincing front is all you need to learn, is the same principle as a landing page test applied face to face. Use it when you want qualitative reactions to a prototype alongside the quantitative click data.
From
GV (Google Ventures)
by Jake Knapp
~15 min read plus resources
- A convincing facade is enough to test; you do not need the real thing
- Five target customers surface most of the problems worth knowing
- Compress research into a week so you decide fast, then move
Open
gv.com →
📄 Article
✓ Link checked
India
Free
Intermediate
Why we picked it
A short interview where Kunal Shah argues margins come from desire, which design creates, rather than from utility alone. It is a crisp Indian case for treating look and feel as a business lever, not vanity. Read it alongside the ship-fast material to decide which side your product sits on.
From
Outlook Business
by Kunal Shah
- Desire, which design shapes, is what lets you charge more.
- Purely utilitarian thinking can leave loyalty and margin on the table.
- Polish is a positioning choice, not decoration.
Open
outlookbusiness.com →
Why we picked it
The permission slip to recruit users by hand, do things manually, and deliver 'insanely great' experiences to your first few customers. The cheapest, most honest way to validate demand is to go get it one person at a time.
From
paulgraham.com
by Paul Graham
~15 min read
- Recruit your first users manually, don't wait for them to come.
- A tiny group of users who love you beats a big group who like you.
- Manual, unscalable effort early is a feature, not a failure.
Open
paulgraham.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 →
