📄 Article
✓ Link checked
India
Free
Beginner
Why we picked it
This piece names the exact trap you are describing: in India, open disagreement often reads as rude, so a prospect will say yes because they sense you want a yes, not because they intend to buy. It goes past diagnosing the problem and gives you concrete moves, asking gentle but firm confirming questions and listening for qualifiers, so you can tell a polite yes from a real one on the call itself. A practical starting point for anyone selling into Indian buyers.
From
Sales & Marketing Management
by Gunjan Bagla
8 minute read
- A yes in an Indian discovery call is often a face-saving reflex, so treat it as a question to probe, not a signal to close on.
- Replace vague agreement-seeking with specific confirmation (for example, do you mean yes, you will place an order this quarter) so the prospect has to commit to something concrete.
- Listen for conditions, qualifiers, and indirect hedges, they are usually where the real hesitation lives when a direct no feels impolite.
Open
salesandmarketing.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
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 →
📖 Book
✓ Link checked
Paid
Advanced
Why we picked it
The foundational text of customer development, 'get out of the building' started here and became the backbone of the Lean Startup. Steve Blank's own site is the primary source.
From
steveblank.com
by Steve Blank
~370 pages
- The biggest risk isn't building wrong tech, it's building something nobody wants
- Customer discovery: test your hypotheses with real customers before scaling
- Separate customer development from product development as parallel processes
- Search for a repeatable business model before you try to execute one
Open
steveblank.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
Intermediate
Why we picked it
This is a catalogue of the specific ways founders sabotage their own sessions, including talking too much, asking hypothetical questions, and reacting visibly to what the user does. Skim it after your first test and you'll probably recognize at least one mistake you just made.
From
Nielsen Norman Group
- Poor or leading questions produce data you can't actually act on.
- Asking someone to predict their future behavior is unreliable.
- Recruiting the wrong participant undoes everything else you do right in the room.
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
A checklist you can run your actual call script against before you place the calls. It catches the specific phrasing habits, like double barreled or leading questions, that quietly invite a polite agreeable answer. Use it as a five minute edit pass on your questions the night before a call, not as background reading.
From
Nielsen Norman Group
by Maria Rosala
~8 min read
- Avoid double barreled questions that bundle two things into one answer.
- Do not phrase a question so it hints at the answer you want.
- Pilot test your questions on one person before you run them on everyone.
Open
nngroup.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Cohen goes straight at the founder self-deception in the question: a room full of enthusiastic yeses is not validation unless people commit money or a concrete next step. He is blunt about the gap between what founders tell themselves and what actually happened in the room, which matches the silence-after-the-call problem exactly. A good essay to reread whenever you feel tempted to call a friendly meeting a win.
From
A Smart Bear (Jason Cohen)
by Jason Cohen
~15 min read
- Ten people saying they would buy is the only kind of validation that counts, not general enthusiasm.
- A founder's hubris about future buyers usually outruns any evidence they actually have.
- If nobody has committed money or a real next step, you have not validated anything yet.
Open
longform.asmartbear.com →
📄 Article
✓ Link checked
Freemium
Beginner
Why we picked it
A two minute companion to the longer HBR piece above, this is the one line version of our short answer you can forward to anyone in a hurry: skip the survey, have the conversation, ask the follow up. Keep it as the quick reference you send a skeptical teammate.
From
Harvard Business Review
- Open ended conversation surfaces the why that a rating scale cannot.
- A dozen genuine interviews usually give you a complete enough picture to act on.
- Save the survey for later, once you know what you are actually trying to size.
Open
hbr.org →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Maurya gives you an actual script structure for a problem interview, including his own correction to an earlier version that leaned on speculative questions. It replaces vague what are your challenges questions with tell me about the last time, which forces a specific story instead of a polite generality. Print this and bring it to your next five calls.
From
Ash Maurya (LEANFoundry)
by Ash Maurya
~15 min read
- Replace speculative challenge questions with tell me about the last time you faced this.
- Explore the customer's worldview before you mention any solution at all.
- A good problem interview produces evidence that either supports or refutes your assumption, not just warm agreement.
Open
blog.leanstack.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
The research-backed classic on consultative selling, the antidote to 'pushy salesperson' instincts. Its Situation-Problem-Implication-Need framework is exactly how founders should run calls.
From
McGraw-Hill
by Neil Rackham
book (~200 pages)
- Ask Situation, Problem, Implication, and Need-payoff questions in sequence.
- In complex/high-value sales, listening beats pitching.
- Make the cost of the unsolved problem vivid before proposing a solution.
- Closing hard works for small deals; discovery wins the big ones.
Open
amazon.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
A clear, short explainer on why asking friends (or anyone) what they want produces false positives, and how to interview for the problem instead. It names the exact trap you fell into: reading politeness as validation. Good as a quick primer to hand a cofounder before your next round of conversations.
From
NYU Entrepreneurship
by Frank Rimalovski
8 min read
- Friends and family skew positive because they want you to win
- Interview for the problem and their current behavior, not for approval of your product
- Genuine signal is specific past action and cost, not enthusiasm about the future
Open
entrepreneur.nyu.edu →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
This essay is the clearest explanation of why stated preference and revealed preference diverge, with a concrete example of people saying one thing and clicking another at scale. It gives you the underlying reasoning for why what broke last time and what you use today beat any question about liking or wanting something. Good to read once, mostly to arm yourself against your own optimism when a call goes well.
From
UX Tigers
by Jakob Nielsen
~10 min read
- What people say they want and what they actually do are frequently two different things.
- Behavioral, revealed data is more trustworthy than a verbal preference collected in an interview.
- Design your discovery process to observe or ask about actual behavior wherever you can, not stated intent.
Open
uxtigers.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
Meyer's framework classifies India as a high-context culture, where meaning is layered and read between the lines rather than stated plainly, which is the cultural mechanism behind the polite yes in the question. This gives you the why behind the pattern, not just tactics for working around it, and is useful if you also manage or sell across other countries with different context norms. Read the India and high-context chapters even if you skim the rest.
From
Erin Meyer
by Erin Meyer
~280 pages
- India sits toward the high-context end of Meyer's scale, where messages are often read between the lines rather than stated directly.
- High-context communication is not dishonesty, it is a different default for how directness is signaled.
- Adjust your questions and your reading of silence to the context style of the person in front of you, not your own default.
Open
erinmeyer.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 →
✍️ Essay
✓ Link checked
Freemium
Intermediate
Why we picked it
Gupta names the Mom Test problem directly, that people in interviews behave like your mom and unconsciously lie to keep you happy, and pairs it with concrete fixes like using visual prototypes to surface real objections instead of polite ones. It is a good next step once you have the basics down and want sharper techniques for a conversation you know will be biased.
From
Aakash Gupta
by Aakash Gupta
- Leading questions like do not you think this is easier will always get you a biased answer
- Showing a prototype instead of describing an idea makes it easier for people to object honestly
- Deliberately include current, potential, and churned users, not just people who already like you
Open
news.aakashg.com →
