📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
The thing that drains most founders is treating research as a big occasional project, so it always feels heavy. Teresa Torres makes the opposite case: one small, regular touchpoint with users each week becomes a keystone habit that quietly pulls the rest of your discovery along with it. For a solo founder, this is the mindset shift from dreading research to running it as a light, repeatable routine instead of a weekly ordeal.
From
Product Talk
by Teresa Torres
About a 10 minute read
- A small weekly customer touchpoint compounds: once it is a habit, prototyping and testing start happening more naturally too.
- Frequency beats depth: short, regular conversations keep you learning continuously instead of front-loading one exhausting research sprint.
- Automate the boring part (recruiting) so the habit survives the weeks you feel busy or low on energy.
Open
producttalk.org →
📖 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
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
Intermediate
Why we picked it
Portigal has run professional research interviews for over 25 years, and this book is the deeper craft manual once you have the basics down. It covers the awkward moments, like what to do with silence or a rambling answer, that a shorter guide will not prepare you for. Read it after Mom Test or Deploy Empathy when you want to get genuinely good at the skill rather than just competent at it.
From
portigal.com
by Steve Portigal
- Silence and pauses are tools, not failures, in an interview
- Plan for the messy middle: rambling answers, tangents, and defensiveness
- Good synthesis after the call matters as much as the call itself
Open
portigal.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 →
📄 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
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 broader companion to the leading questions piece, this covers the shape of a whole interview, from opening rapport to the order of questions to how to probe without steering. Read it once the basic don't lead the witness rule is second nature and you want to tighten the rest of the conversation.
From
Nielsen Norman Group
by Jakob Nielsen
10 minute read
- Start broad and open before narrowing into specifics
- Probe with silence and tell me more instead of suggesting the next detail yourself
- Keep the questions you ask separate from the interpretation you do afterward
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
A method for finding exactly where your customers already gather online, the forums, subreddits, and groups where they post their problems. Instead of guessing, you learn to trace your audience to their watering holes and read what they struggle with in their own words. This directly answers the where do I even look question.
From
Stacking the Bricks
by Alex Hillman
~12 min read
- Find the online places your audience already gathers
- Read their real complaints in their own words
- Their jargon and pains show you how to reach them
Open
stackingthebricks.com →
🧵 Thread
✓ Link checked
Free
Beginner
Why we picked it
This is a real thread of solo and small team founders admitting the exact fear in your question, and working through it together in the comments. The most useful reframe that keeps surfacing: treat the call as one business owner asking another about their problems, not a sales pitch. Worth reading for the reassurance alone, this fear is common and beatable, not a personal flaw.
From
Indie Hackers
- Reframe the call as peer to peer, not seller to buyer
- Other technical, introverted founders share the exact same dread
- Small, low stakes practice conversations lower the anxiety over time
Open
indiehackers.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 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 →