Idea Validation
Stop building things people don't want by moving from opinion to evidence-based development.
Help the user with idea validation using insights from 31 guests and posts across Lenny's Podcast and Newsletter.
How to Help
- Clarify the Core Hypothesis - Help the user define the specific problem, target audience, and the most 'risky' assumptions using the Founding Hypothesis Scorecard.
- Select a Validation Path - Guide the user through choosing between the 'Listening Path', 'Manual Path', or 'Self-Serve Path' based on their proximity to the problem.
- Design Low-Fidelity Experiments - Recommend specific 'Wizard of Oz' or 'Fake Door' tests to simulate the solution without building a backend.
- Evaluate Signal Quality - Help users distinguish between polite interest and real market pull by looking for financial commitment or high-effort usage.
Core Principles
First-Principles De-risking
Bangaly Kaba: "Someone says, 'Hey, you know what? This would be great to build.' And you go pull data to go justify why that would be great to build. Call that identify, justify, execute. First you have to really understand from first principles what is actually going on."
True de-risking starts with understanding the core problem from first principles before looking for data to justify a specific solution.
Maintaining Prototype Momentum
Grant Lee: "We would have an idea in the morning, come up with some sort of functional prototype, recruit a bunch of people that are legitimately good prospective users, but have zero skin in the game, ship fast so people can start playing with it. In the afternoon, we're already running pretty full scale experiment."
Build functional prototypes within hours of conceiving an idea to maintain speed and identify usability flaws before wasting development cycles.
Direct User Feedback Loops
Gustaf Alstromer: "If I drill down what makes companies fail, it's quite simple. It's just like they don't talk to users, which means they don't find product market fit. And if they don't find product market fit, nothing else really matters."
Achieve product-market fit by talking to customers directly and immediately to learn if you are building something people actually want.
Workflow Compression
Oji Udezue: "So the zone of benefit works as a framework because people will not pay for things that don't either really shrink the workflow that they're doing or doesn't give them superpower. So the same amount of time, but twice as much output. But the most important thing is that it has to be noticeable."
A problem is only worth building for if your solution offers a visible and massive compression of the existing customer workflow.
Templates & Frameworks
- Four B2B Idea Validation Paths (How to validate your B2B startup idea) - A framework for choosing which validation strategy to use based on your context as a founder. Each path represents a different level of up-front investment and
- B2B Idea Validation Interview Process (How to validate your B2B startup idea) - A synthesized process for conducting validation interviews based on patterns across multiple successful B2B founders
- Four Signs Your B2B Idea Has Real Pull (How to validate your B2B startup idea) - A checklist of signals that indicate genuine market demand vs. polite but hollow interest
- Vanta's Manual Validation Process (How to validate your B2B startup idea) - How Christina Cacioppo validated Vanta's idea by manually creating SOC 2 compliance reports before writing any code
- Founding Hypothesis Scorecard (Introducing the Foundation Sprint: From the creators of the Design Sprint) - A scorecard with testable questions for each element of the Founding Hypothesis, used to systematically validate or invalidate your product strategy
- Pre-Product Invoice Test (How to know if you've got product-market fit) - A pre-product PMF validation technique where you literally try to get potential customers to pay you before the product exists.
- Ugly Baby Validation (1,000,000) - A framework for getting early validation on a new creative project by finding the right motivators
- DoorDash's paloaltodelivery.com MVP (How the biggest consumer apps got their first 1,000 users) - How DoorDash validated demand with a simple website with PDF menus and printed flyers at Stanford
See references/artifacts.md for the full list with details.
Questions to Help Users
- "What is the single most risky assumption that must be true for this idea to succeed?"
- "Are you getting feedback from cold prospects or just people in your network who want to be nice?"
- "How many steps does your solution remove from the user's current manual workflow?"
- "If you had to launch a 'fake door' experiment tomorrow with zero backend, what would it look like?"
- "Has a potential customer offered to pay for this before you have even built it?"
- "What is the 'must-have' feature that, if missing, would cause the user to walk away immediately?"
Common Mistakes to Flag
- Confusing Politeness with Validation - Mistaking 'this looks cool' for 'I will pay for this' leads to building products that lack real market pull.
- Building Before Testing - Investing heavy engineering resources into a full backend before validating the front-end value proposition wastes months of time.
- Relying on Warm Leads - Feedback from friends or family is biased and rarely provides the 'pure' signal needed to judge an idea's merit.
- Averaging User Feedback - Failing to segment feedback between skeptics and early adopters can lead to a watered-down product that serves nobody well.
Deep Dive
For all 33 sourced insights from 31 guests, see references/guest-insights.md
- Customer Interviews
- Continuous Discovery
- Product Experiments
- Defining Icp