Why 'What Do You Think?' Is the Wrong Question
I used to ask people what they thought. All the time.
Here's the problem. That question isn't really about your product. It's a social question. People hear "what do you think" and their brain answers "how do I respond to be encouraging."
They're not evaluating your work. They're managing the conversation.
Ask a friend what they think of your idea and you'll almost always get something polite. Not because they're lying. Because without something real in front of them, they're guessing, and guessing tends to be kind.
What a Half-Built Demo Actually Measures
A demo forces a decision. Do they click the button or not. Do they get stuck or not. Do they lean in or check their phone.
That's real data. An opinion is not.
Half-built demo feedback is the reaction you get from putting an unfinished, working prototype in front of someone and watching what they do with it. It captures behavior under real constraints instead of speculation.
You're not asking them to imagine your product. You're watching them use it.
The Behavior Gap: Opinions vs. Reactions
There's a gap between what people say and what people do. Anyone who's run a business has felt this gap personally.
Someone tells you "I'd definitely use this." Then you ship it and they never open it once.
That's not because they lied to you. It's because people are bad at predicting their own future behavior. Especially with someone they know is emotionally invested in the answer.
A demo skips the prediction step entirely. You don't have to guess what they'll do. You just watch.
How to Ship a Half-Built Demo for Feedback (Not a Finished Product)
Here's the short version: one real flow, no polish.
It should be finished enough to use for its core action. Everything else can be rough, or fake, or missing entirely.
A good test: if it takes you more than a few minutes to explain what's not real yet, it's not rough enough. You're spending your energy in the wrong place.
People don't need a polished product to give you real signal. They need one thing that actually works.
Reading Demo Feedback: What Silence, Confusion, and 'Can I Try It' Actually Mean
Silence usually means confusion, not agreement. If someone goes quiet, they're probably trying to figure out what they're looking at.
Confusion tells you exactly where your explanation is doing work your product should be doing.
And "can I try it" is the best feedback you'll ever get. It means the thing in front of them is real enough to want.
When you show a demo, don't ask what they thought of it. Ask what they'd do next. Questions like "what were you expecting to happen here" or "would you use this tomorrow" reveal behavior and intent. Skip the questions that let them critique your work instead of react to it.
When Asking Is Still Useful (And When It Isn't)
Asking isn't useless. It's just aimed at a different job.
Surveys and interviews are good for understanding a problem before anything exists to build. They're good for context, motivation, and finding out what's actually bothering someone.
A demo is good for testing whether your solution to that problem actually works.
Use asking to find the question. Use a demo to test the answer.
FAQ
Why is demo feedback more valuable than asking people what they think?
A demo forces people to react to a real thing instead of imagining a hypothetical one, which surfaces their actual behavior, confusion, hesitation, excitement, instead of their polite opinion. Asking "what do you think" invites people to answer a social question about how they should respond, not a product question about whether it works.
What is 'half-built demo feedback'?
It's the reaction you get from putting an unfinished, working prototype in front of someone and watching what they do with it. It's more reliable than survey or interview feedback because it captures behavior under real constraints instead of speculation.
How unfinished should a demo be before you show it to someone?
It should be finished enough to use for its core action but rough everywhere else, one real flow, no polish. If it takes more than a few minutes to explain what's fake, it's not rough enough yet.
What questions should you ask after showing a demo?
Ask what they'd do next, not what they thought of it. Questions like "what were you expecting to happen here" or "would you use this tomorrow" reveal behavior and intent. Avoid questions that let them evaluate your work as a critic instead of react to it as a user.
Why do people give inaccurate feedback when you just ask them?
People are bad at predicting their own future behavior and tend to answer to be encouraging rather than accurate, especially with someone they know is emotionally invested. Without something concrete to react to, their answer reflects politeness and imagination more than real judgment.
Is survey or interview feedback ever more useful than a demo?
Yes. When you need to understand context, motivation, or a problem space before anything exists to build, surveys and interviews are better for discovering problems. Demos are better for validating solutions. Use asking to find the question, and use a demo to test the answer.