When to use it
Use Customer Discovery when you've been building based on assumptions and haven't had real conversations yet, when you're about to make a major product or pricing decision, or when your pitch feels polished but nobody has actually pushed back on it.
Especially powerful if you've been in "build mode" and haven't stepped back to test whether anyone actually cares. It's the tool for anyone in The Untangle who needs to hear from real customers before committing further.
How it works in The Studio
Here's how a session works with WAiDE:
Sample output
Here's what a Customer Discovery session looks like in practice:
What you get
A qualitative discovery brief capturing which assumptions held, which were challenged, key insight from all persona conversations, and 1–2 concrete next steps.
Often reveals a significant mismatch between your assumed differentiator and what customers actually care about. Your downloadable report includes the full persona exchange log, WAiDE's pattern synthesis, and relevant Wade programs for the next stage.
Foundation
Developed by Steve Blank in "The Four Steps to the Epiphany" (2005) and popularised by Eric Ries in "The Lean Startup." Core principle: customer assumptions are hypotheses, not facts. Used at Y Combinator, Stanford d.school, IDEO, and by Wade Institute in its founder programs.
Why it works
Customer Discovery works because new ventures — whether startups or internal innovation projects — are built on a stack of assumptions, and those assumptions are almost never tested before resources are committed to them. The canonical failure pattern is: team builds product, product launches, customers don't adopt at the rate assumed, team blames marketing or execution when the real problem was the original customer assumption was wrong. Customer Discovery moves the test to before the build, when correction is cheap.
Steve Blank's specific contribution was naming the problem precisely. Before "The Four Steps to the Epiphany", the dominant mental model was that a new venture was a smaller version of an existing business — and that the standard business playbook (hire a sales force, build a product, scale the organisation) applied. Blank argued that a startup is not a smaller version of a large company; it's an organisation in search of a repeatable and scalable business model. That search requires a fundamentally different method, and Customer Discovery is that method.
The discipline of getting out of the building — Blank's shorthand for the practice — addresses a specific cognitive failure mode: the team's enthusiasm for their own idea. Inside any founding team, there is always enormous psychological investment in the solution. Customer Discovery creates a structured reason to speak with people who don't share that investment, and a protocol for listening to what they actually say rather than hearing confirmation of what you hoped to hear. The discipline is in not pitching — asking and listening instead.
The mechanism: Customer Discovery converts the venture's key beliefs into explicit hypotheses and then designs the minimum observable evidence that would confirm or disconfirm each one. This is not just good research practice — it's a discipline that protects founders from the most common and most expensive mistake in entrepreneurship: falling in love with the solution before understanding the problem.
Frequently asked questions
How many customer conversations do I need before I have enough to act on?
There's no fixed number, but a useful signal is saturation: when the themes you're hearing stop changing and start repeating, you've likely talked to enough people in that segment. For early-stage discovery, 15-20 conversations with your target customer profile usually produces enough signal to make a directional decision — not certainty, but enough to know whether your core assumptions are roughly right, roughly wrong, or more complicated than you thought.
How do I avoid leading the witness — getting the answers I want to hear?
Ask about behaviour and experience, not opinions about hypotheticals. "Would you use this?" is a hypothetical and almost always produces yes. "Walk me through the last time you had this problem — what did you do?" is behavioural and produces real data. The Rob Fitzpatrick test from "The Mom Test" applies here: if your own mother would give the same answer, the question is too leading. Ask about their world, not about your solution.
What's the difference between Customer Discovery and market research?
Traditional market research asks people what they want and aggregates the answers. Customer Discovery is a scientific method applied to business hypotheses: it starts with a specific belief, designs an interview or observation to test it, and updates the belief based on evidence. It's qualitative and iterative rather than quantitative and retrospective. The goal is not to describe a market — it's to understand whether a specific mechanism (your solution) would work for a specific person in a specific situation.
Does Customer Discovery apply to corporate innovators, or just startup founders?
It applies to any innovation that serves a customer whose problem isn't yet fully understood — which includes the vast majority of corporate innovation projects. Internal teams are often even more subject to assumption-driven thinking than startups, because they have existing budgets and organisational support that can sustain projects long past the point where a startup would have pivoted. The discipline of getting out of the building applies equally to anyone building something new for someone else.