1of 6
Derisking: Which failed assumption would kill the idea?
Before investing in a polished prototype, find the assumption your idea can't survive getting wrong. Then test it.
Adapted by the EWOR Team from an article on EWOR (opens in a new tab)4 min read
A prototype is only as useful as the assumption it tests
It's tempting to build the prototype your team already knows how to make. But a working prototype doesn't necessarily mean you're any closer to a viable startup. The more important question is: what would have to be true for this idea to work, and what happens if it isn't?
Start with the assumption that could bring the whole concept down. Find the least costly test that can credibly tell you whether it holds. Otherwise, you risk spending time polishing a prototype that answers an easy question while the biggest uncertainty remains untouched..
List what has to be true
Every startup idea rests on three things:
- Desirability: Do the intended customers have this problem, and will they choose the outcome you're offering?
- Feasibility: Can you deliver the essential function with the required performance, reliability and safety?
- Viability: Can the business create, deliver and capture enough value to sustain itself?
Make each assumption specific enough to prove wrong. Saying “customers value simplicity” doesn't tell you much. Name the customer, the situation and the behaviour you'd expect to see. Instead of assuming the technology will work, define the critical capability it needs to deliver. For viability, identify the customer behaviour or economics your business model depends on.
Include the things you're treating as facts simply because you believe them. Confidence isn't evidence, and assumptions are hardest to challenge when you haven't acknowledged them in the first place.
Find the claim the concept cannot survive without
For each assumption, ask yourself:
- If this turns out to be false, can the idea still work without becoming a fundamentally different concept?
- How uncertain is it, given the evidence you already have?
- What's the cheapest credible way to test it?
- What harm or irreversible cost could the test create?
Focus first on assumptions that are both uncertain and consequential. Cost matters when choosing between credible tests, but it shouldn't push a safety-critical question aside in favour of an easier, less informative experiment.
This is your leap-of-faith assumption: the claim that must hold for the idea to work. Give it a test, and decide in advance what result would make you stop, rethink the concept or change direction.
Know when feasibility should lead
For many startups, it's cheaper to test whether people want an outcome than to prove you can deliver it at scale. If that's true for your idea, start with desirability. There's little point in perfecting a technical solution that nobody wants.
But sometimes feasibility is the biggest question. If your concept depends on complex hardware or a capability at the edge of what your team can deliver, you may need to test the technology first. Otherwise, you can't honestly represent the experience you're asking customers to evaluate.
The rule isn't to always test desirability first. It's to test the most critical uncertainty first, using the least costly credible method.
Isolate critical function and critical experience
Some ideas depend on a function working as intended. Others succeed because of the experience they create. Work out which matters most:
- Critical function: The capability without which the user's problem remains unsolved.
- Critical experience: The interaction or outcome that makes users choose the product or keep using it.
Your test can focus on one without proving the other. A function test doesn't need to resemble a finished product. An experience test might use a simulation, but be clear about what the simulation can't yet demonstrate.
Give the next test a clear brief
Before building or testing anything, write a one-page brief covering:
- Assumption: What needs to be true, and which category does it fall into?
- Stakes: Why would being wrong matter?
- Evidence: What supports or contradicts the assumption so far?
- Test design: Who or what will be tested, how, and against which observable threshold?
- Constraints: What will the test cost, how long will it take, and what safety boundaries apply?
- Decision: What result would support the idea, challenge it or leave the question unresolved?
- Remaining unknowns: What might the test still fail to tell you?
Keep exploring while you test. Customer interviews, expert input, competitor analysis and prototype observations can all uncover assumptions you hadn't considered.
Spend the next effort where being wrong would matter most. Agree what the result will change so the experiment can redirect the work, not just confirm the founder’s preference.





No comments yet.
Be the first to comment on this signal.