To get unbiased feedback, don't mention your product. Instead, ask prospects about their #1 challenge. If they organically bring up the problem your product solves, you've found a real pain point and strong market pull.

Standard "discovery interviews" are often a form of "playing founder." It's arrogant to believe a few 30-minute conversations can yield the deep insights needed to build a game-changing product. True understanding comes from immersing yourself in the customer's work, not just casually interviewing them.

Amazon's 'Working Backwards' process begins with the end: a press release (PR) and frequently asked questions (FAQ). This low-cost exercise forces teams to be hyper-focused on customer problems and value proposition from the outset, long before any code is written. It helps filter ideas based on customer impact.

Structure discovery into two distinct conversations for maximum effect. The first meeting should focus exclusively on uncovering the customer's blocked goals (demand), without mentioning a product. Use the second meeting to validate if a high-level solution sketch (supply) gets ripped out of your hands.

Don't wait until your product is built to start selling. By scheduling a high volume of meetings (e.g., 3-4 per day per founder), you can use those conversations not to sell, but to discover true customer pull, refine messaging, and define your product based on real-time feedback.

Rushing to market without validation is a recipe for failure. Instead, engage potential buyers and proposition leads as 'critical friends' in focus groups. Use their feedback to build a white paper, refine messaging, and create a product they actually need, even if it takes a year.

Instead of building an MVP, pitch a one-liner about your solution to a target audience and gauge their reaction. Passionate, unsolicited stories about their pain points signal strong problem-solution fit. This method provides objective validation with minimal resources.

Early demos shouldn't be used to ask, "Did we build the right thing?" Instead, present them to customers to test your core assumptions and ask, "Did we understand your problem correctly?" This reframes feedback, focusing on the root cause before investing heavily in a specific solution.

De-risk new product initiatives by validating them directly with the market using low-fidelity prototypes like sketches. By building a following and an adoption list before development begins, you create undeniable proof of demand that can overcome internal resistance and ensure a successful launch.