What Is a Discussion Prototype? Definition + Example

A discussion prototype is the lowest-fidelity prototype you can make: a rough sketch, diagram, or simple mockup whose only job is to make an abstract idea concrete enough to have a focused conversation with a customer. It exists to spark reactions and gather qualitative feedback, not to test usability.

Quick Answer: A discussion prototype is a deliberately crude artifact — a napkin sketch, a boxes-and-arrows diagram, a paper mockup — used to give a customer something specific to react to during an interview. In Testing Business Ideas, Bland and Osterwalder classify it as a low-cost, fast-to-build tool that produces weak, qualitative evidence. Its purpose is to prompt richer conversation, not to measure whether people can use your product.

Talking about an idea in the abstract produces vague, polite answers. Put a rough drawing in front of a customer and the conversation sharpens instantly — they point, they object, they start redesigning it for you. That shift is the entire reason a discussion prototype exists.

How a Discussion Prototype Works: It Prompts a Conversation, Not a Test

A discussion prototype works by giving the customer a concrete object to respond to, so their feedback attaches to something specific instead of floating in the abstract. The artifact is a conversation prop, not a product.

Its only job is to make the idea tangible. People struggle to react to a described concept but react effortlessly to a thing they can see. A sketch, a flow diagram, or a single mocked-up screen gives the interviewee a surface to push against — and their pushback is the data you came for.

It deliberately stays rough. Testing Business Ideas places the discussion prototype at the bottom of the fidelity ladder precisely because low fidelity is a feature. A polished mockup invites critique of fonts and colors; a hand-drawn one keeps the customer focused on the idea. See what is prototype fidelity for where this sits relative to more finished artifacts.

It produces qualitative signal only. You learn what confuses people, what excites them, and which parts they ignore. You do not learn whether they will pay, whether they can complete a task, or how big the market is. Treating a warm reaction as validation is the classic misread — enthusiasm in an interview is a hint to investigate, never proof.

A Concrete Discussion Prototype Example

Here is what a discussion prototype looks like in practice. A founder building a tool to help freelancers manage late invoices sketches the core idea before writing any code — the artifact is intentionally minimal.

The build. On a single sheet, the founder draws three boxes — "invoice sent," "reminder auto-fires," "payment tracked" — connected by arrows, plus a rough sketch of one screen showing a list of overdue invoices with a red flag next to each. Fifteen minutes of drawing, no tools beyond a pen.

The interview. The founder shows it to a freelance designer and says, "Walk me through what you think this does." The designer responds: "Wait, does it actually send the reminder, or just remind me to send it? Chasing clients is the part I hate." That single reaction reframes the value proposition — the pain is not tracking, it is the awkwardness of chasing.

The takeaway. No line of code, no usability test, just a rough drawing that surfaced a sharper problem than the founder had assumed. That is a discussion prototype doing its job: converting a vague idea into a focused, revealing conversation.

Discussion Prototype vs. Storyboard: How They Differ

Both are low-fidelity artifacts used early, but they answer different questions. A discussion prototype makes a feature or concept concrete; a storyboard makes an experience over time concrete. The table below contrasts them qualitatively — no metrics implied.

Takeaway: Reach for a discussion prototype when you need a fast reaction to one concept, and a storyboard for validation when the thing you are testing is how a whole experience unfolds. They complement each other rather than compete.

When to Use a Discussion Prototype in Interviews

Use a discussion prototype at the earliest, foggiest stage of exploration — when you have an idea but little evidence, and your biggest risk is that you have misunderstood the problem. It is a discovery tool, not a validation verdict.

Use it during customer interviews, not instead of them. The prototype is a prop inside a conversation. Introduce it a few minutes in, after the customer has described their situation in their own words, so their reaction builds on real context rather than leading it. It fits naturally into a broader customer research practice.

Ask open, non-leading questions. "Walk me through what this does" and "what would you change?" invite honest reactions. "Would you use this?" and "isn't this great?" invite politeness. The whole value collapses if you fish for approval.

Know when to graduate past it. Once you have heard the same reactions repeatedly and refined the concept, a discussion prototype stops teaching you anything new. That is the signal to move up the fidelity ladder toward artifacts that test behavior — whether people click, complete tasks, or commit — because a sketch will never give you that.

Key Takeaways

• A discussion prototype is the lowest-fidelity prototype — a sketch, diagram, or rough mockup made to spark a focused conversation with a customer.
• Its purpose is reactions, not usability data. It makes an abstract idea concrete enough to critique, nothing more.
• It produces weak, qualitative evidence. In Testing Business Ideas, it sits at the bottom of the fidelity ladder as a fast, low-cost exploration tool.
• Roughness is intentional. A crude artifact keeps the customer focused on the idea instead of the polish.
• Use it early, inside interviews, when your main risk is misunderstanding the problem.
• Ask open questions and avoid fishing for approval — enthusiasm is a hint to investigate, never proof.
• Graduate past it once reactions repeat and you need evidence of real behavior.

Frequently Asked Questions

Is a discussion prototype the same as a low-fidelity prototype?

A discussion prototype is a type of low-fidelity prototype — the lowest-fidelity kind. "Low fidelity" describes any rough, unpolished artifact; a discussion prototype is specifically the sketch or diagram used to prompt a conversation and gather reactions in an interview, rather than to test whether someone can use a product.

What kind of evidence does a discussion prototype produce?

Qualitative and weak evidence only. You learn what confuses, excites, or bores a customer, and which parts of an idea they care about. You do not learn whether they will pay, whether they can complete a task, or how large the market is. Treat the reactions as directional hints that guide stronger experiments later.

How do I make a discussion prototype?

Spend fifteen minutes, not fifteen hours. Sketch the core idea on paper — boxes and arrows for a flow, a single rough screen for an interface, a simple diagram for a service. The goal is something concrete enough to point at and discuss. Deliberate crudeness keeps the customer focused on the concept, not the visual polish.

When should I stop using a discussion prototype?

Stop when reactions start repeating and the sketch no longer teaches you anything new. Your open questions are being answered the same way each time, and your next risk is behavioral: will people actually act? Move up to a higher-fidelity prototype that tests what customers do, not just what they say.