how to test a product idea before you build it

write down what you're trying to learn

“is this a good idea?” is too broad.

who is it for? what problem would it help them with? what would they receive? why would they choose it over what they do now?

put that in plain language. you don't need a brand identity to explain a useful product.

choose the uncertainty that matters most. maybe you don't know whether the problem is painful enough. maybe people recognise the problem but don't understand your proposed solution. those need different conversations.

talk to people who have the problem

find people who actually deal with the situation your idea is meant to address. a friend being supportive isn't the same as a potential buyer recognising a need.

ask about what happens now. how do they handle it? what's difficult? have they tried anything else?

listen before presenting your answer. if you start by explaining why your product is brilliant, you make it harder to hear the part that doesn't fit.

keep their words. “I'd love that” tells you less than a specific explanation of where the product would be useful, what they'd expect, and what might stop them choosing it.

give people something concrete to respond to

here's an illustrative example: you want to make a planning workbook for people running their first community event.

rather than building the whole workbook, you could show a short description and a sample page. explain who it's for, what it helps them plan, and what the finished version would include.

make the status clear. a concept, a sample, and a finished product aren't interchangeable.

if you're testing interest through a waitlist, say what joining means. don't call it an order or imply that a product exists when you're still deciding whether to make it.

use a waitlist as a signal, not a verdict

my original letter describes using waitlists before a launch. they give interested people a next step and give you a way to continue the conversation.

make that step easy to understand. what will they hear about, and when might they hear from you?

then share the idea with relevant people. a page nobody sees can't tell you much about demand.

record what you shared, who it was intended for, and what happened. you don't need to collect lots of personal information to learn whether people understand the offer.

someone joining a list has expressed interest. they haven't necessarily agreed to pay. keep that distinction when deciding what to build.

look at the questions as well as the signups

if nobody joins, investigate before declaring the idea dead. did relevant people see it? did they understand it? did the problem matter to them? was the next step clear?

if people join but keep asking for something different, that's useful too. they may be interested in the problem while wanting another kind of solution.

likes and compliments can feel encouraging. don't treat them as evidence of purchases you haven't made.

write down what you'd need to learn next. that could mean another conversation, a clearer explanation, a revised sample, or deciding the idea doesn't deserve more work right now.

decide the next step before building everything

after the test, make a short decision note:

• who saw the idea
• what they understood and wanted
• what action they actually took
• what is still uncertain
• what I will change or test next

if the evidence is thin, keep the next commitment small. you don't owe an idea a full launch just because you've spent a weekend thinking about it.

being willing to change it is part of the work. the useful outcome is learning what to make, for whom, and why.