🔬 Idea Stress Test

Why do it — and why almost nobody does

Every founder has experienced this: an idea arrives, it seems strong, obvious, elegant. You start talking about it — everyone nods. You feel the energy. And so you start building.

Six months later, you discover the market doesn't care. Not because the idea was intrinsically wrong, but because you never forced yourself to articulate its weakest assumptions before committing to them.

The Idea Stress Test exists to compress this cycle. Before spending a single hour coding, designing or pitching, you answer 7 questions that force you to confront the structural weaknesses of your idea. Not to kill it — to make it more robust or discover early where it really breaks.

What is the Idea Stress Test

The Idea Stress Test is a structured self-evaluation framework of 7 questions designed to identify the most dangerous assumptions in an early-stage idea. Each question targets a specific category of failure: market, problem, solution, competition, distribution, timing and founder-market fit.

The output is not a score. It's clarity: you exit the test knowing which hypotheses you need to validate first — before any investment of time or money.

How to use it

Question 1: Is the problem real and recurring?
The problem has to exist before you arrive. If you need to explain to people that they have a problem, you're selling a vitamin — not a painkiller. The test asks: can you name 5 real people with this problem right now? Can you describe what they do today to solve it (or live with it)?

Question 2: Who is the customer and what do they lose today?
"Everyone" is not a customer. The more precisely you can describe who suffers from this problem — job, context, frequency, cost they bear — the stronger the hypothesis. If you can't describe the first 10 people to call, the customer segment is too vague.

Question 3: Why hasn't this been solved yet?
This is one of the most underrated questions in early validation. If the problem is obvious and the market is large, why doesn't a good solution already exist? The answer is often one of: technical barrier now disappearing, regulatory change, new distribution channel, shift in user behaviour. If you can't answer this, you're probably not the first to try.

Question 4: What does the competition look like, including the status quo?
Your real competitor is rarely another startup. It's what the customer does today: the spreadsheet, the phone call, the manual workaround, doing nothing. Map both: direct alternatives and status quo. If you can't explain why someone would switch from their current solution to yours, you don't have a product yet.

Question 5: What's your unfair distribution advantage?
Great products that reach nobody are worth nothing. The stress test asks: through which channel do you reach your first 100 customers? Do you have a natural distribution advantage — a community, a network, a platform, a partnership? If the answer is "we'll do paid acquisition," you're betting on a mechanism you can't yet afford.

Question 6: Why now?
Timing is one of the most underestimated success factors. Was there something that recently changed — in technology, regulation, behaviour, infrastructure — that makes this idea viable today but wasn't 3 years ago? If you can't explain why now, you might be too early (or too late).

Question 7: Why are you the right team?
Not in the "we're passionate" sense. In the operational sense: do you have specific domain expertise, privileged access, relevant technical skills? Investors call this founder-market fit. The stress test asks you to be honest about it before spending months in a space where you have no structural advantage.

3 common mistakes

1. Answering as if you were the customer
The worst answers are those the founder gives imagining what a hypothetical customer would think. The test works only if the answers are based on real conversations with real people — not on internal projections.

2. Treating weak answers as "to be validated later"
If you can't answer question 3, it's not a detail to address in six months. It's the most important thing to understand before everything else. The stress test is useful precisely because it forces you to look the weakest point in the eye right now.

3. Stopping at the test
The stress test is a starting point, not an end. It tells you which hypotheses to test first. If you answer questions and then don't do Customer Discovery (Step 4), you've done half the work — the less useful half.

Real Examples

Alan (France): Before building their health insurance product, Alan's team ran a systematic stress test on the B2B employer market. The key question was: why now? The answer: digital-native companies in France were dissatisfied with traditional insurers but had no modern alternative. That specific timing hypothesis — not just "health insurance is a big market" — guided the first months of Customer Discovery.

Voi Technology (Sweden): The Voi team tested the timing question aggressively before launching electric scooters in European cities. The regulatory window was opening in several municipalities; the hardware (LiDar-assisted scooters) had just become cost-viable. "Why now" had a precise answer. That answer shaped both the launch market and the first investor pitch.

Gorillas (Germany): The 10-minute grocery delivery idea survived its stress test because the team had a precise answer to "why hasn't this been solved?" Existing players (Deliveroo, Just Eat) had optimised for restaurant delivery — the grocery supply chain was structurally different and required a dark store model nobody had yet built in Europe at that scale.

Recommended Resources

The Mom Test — Rob Fitzpatrick — the essential book for understanding why most customer conversations produce false positives, and how to ask questions that generate real signal. — https://www.momtestbook.com/

The Startup Owner's Manual — Steve Blank — the foundation of Customer Development, with specific frameworks for testing problem hypotheses before building. — https://www.steveblank.com/

IDEO Design Thinking — useful for stress-testing assumptions about user behaviour through rapid, low-cost experiments. — https://designthinking.ideo.com/

Next Step with IdeaLedger

Once you've answered the 7 questions, you have two paths. If most answers are strong, move to Step 3 (Lean Canvas) — you're ready to structure the model. If several answers are weak, go to Step 4 (Customer Discovery) first — you need more signal before anything else. Don't rush: the time you spend here saves months later.