4 ms·
You first need to find out if there's even a market for the problem you think is worth solving. To do that you need to get out of the proverbial building and f
by ASquare 12y ago
You first need to find out if there's even a market for the problem you think is worth solving.
To do that you need to get out of the proverbial building and find people who you think might have the problem and ask them some specific questions that will help you identify whether there is an potential or not.
I reccomend reading "Running Lean" by Ash Maurya as it provides a great framework and sequence of steps to follow to validate your idea
In terms of the kinds of questions you might ask:
A. Customer Segments: Who has the pain?
• How to identify early-adopters? Ask some introductory questions to collect basic demographics that you believe will drive how you segment and qualify your early adopters.
B. Problem: What are you solving?
List (up to) the top 3 problem you believe you are solving
• How does the interviewee rank the top 3 problems?
• What is their pain level for all of these problems: must-have, nice-to-have, don’t-need?
• How do customers solve these problems today? – This is generally the heart of the interview as they do a lot of talking and you ask follow up questions based on their responses.
You are done when you have interviewed at least 10 people and
• can identify the demographics of an early adopter,
• have a must-have problem and • can describe how customers solve this problem today
Hope that helps.
- vitovito 12y agoCame here to write this. I've kept lists of project ideas for years, but the last few years breaks them down into "could have market validation" and "would just be for fun." There's a dozen new ones so far this year. Maybe two of them have any potential for market validation (I'm evaluating one of them right now). The rest are almost certainly projects where, as neat as they would be, there's probably zero chance anyone would pay to solve that problem.