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

1. Clarify the Core Hypothesis - Help the user define the specific problem, target audience, and the most 'risky' assumptions using the Founding Hypothesis Scorecard.
2. 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.
3. Design Low-Fidelity Experiments - Recommend specific 'Wizard of Oz' or 'Fake Door' tests to simulate the solution without building a backend.
4. 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.