A Structured Approach to Ideation and Validation (I will not promote)

Hi all, I used to work in VC and wanted to share some startup knowledge and insights from startup founders I know. Recently, I interviewed a friend of mine who built an AI Robotics startup ("Hivebotics") that creates automated toilet-cleaning robots. I can't post the full article because of Reddit's word limit, so I'll be posting it in sections here instead. This first section of the transcript goes through his approach to ideation and validation. Enjoy and let me know what you think! (I will not promote) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ # (1) Ideation and Validation **Problem-Market-Solution Framework** I like to think of startup ideation and validation using this framework: 1. **Problem**– What exactly are you solving? 1. **Observation**– How you identify a problem to work on 2. **User Research**– How you further understand that problem 2. **Market**– Is there a large enough market for solving this problem? 1. **Size**– How many people experience this same problem? 2. **Demand**– How many of those people are willing to pay for the solution? 3. **Solution**– Your answer to the problem 1. **Desirability**– Whether people actually want your solution 2. **Feasibility**– Whether building the solution is practical and realistic 3. **Viability**– Whether your solution can generate revenue **Problem** You always need to start problem-first, which is something that was really drilled into me during my time at Stanford. Too often, founders rush to build solutions first—apps or products they find exciting—without confirming whether there's any real demand for it. The first step is always to identify a specific problem, then further understand its scale, urgency and further details by talking to potential users. * **Observation**– To find problems, observation is key. People may not even realise the inefficiencies in their processes until you point them out. That’s why interviews and field research are so important. There are problems all around us, so it's simply a matter of going out, paying attention and being attuned to them as they occur. * **User Research–** To further understand the problem, conducting user research by interviewing potential customers is essential. Personally, I like to use the "Mom Test" when I conduct interviews to avoid biased and generic feedback. Don’t just ask theoretical questions and avoid being too specific—observe how your potential users work, ask about pain points, and use broad, open-ended questions to ensure you aren't leading them to a specific answer. **Market** Once you've found an actual problem and talked to enough potential users to really understand its specific pain points, the next step is to determine the market size and demand for a solution. * **Size–** Determining the market size is essential because it determines whether or not it's commercially worthwhile to pursue the problem and develop a solution for it. You need to determine if there are enough potential customers out there experiencing this problem to gauge the market size. There's no secret strategy for this; you have to interview as many potential users as possible to confirm that it's a widespread problem in the industry. * **Demand–** Make sure that you're working on a problem that people will gladly pay to have solved. Even if the problem is large enough, you have to make sure it's *painful* enough to warrant a paid solution. If many people experience the same problem, but aren't willing to pay for a solution, then you don't have a market and should look for a different problem to validate. Another way of looking at it is that your true market size is the number of potential customers actually willing to *pay* for the solution to the problem, not the number of people simply experiencing the same problem. **Solution** When validating a potential solution to the problem, I would look at the 3 factors of *desirability, feasibility* and *viability.* * **Desirability–** the degree to which a solution appeals to people and fulfills their wants and needs. Without strong desirability, even the most technically advanced or economically practical product is unlikely to succeed. The best way to test this is to secure financial commitments early on during the proof-of-concept stage. Most people are polite, so they may simply tell you that your startup's product is good even if it's not. However, if they're actually willing to pay for the solution, this is actual evidence of your product's desirability. Don't just ask people if they would pay for it; actually see whether they will pay for it. * **Feasibility–** whether a product can be built using existing technical capabilities. A lack of feasibility makes it challenging or impossible to develop the product, no matter how appealing it might be to users or how promising its financial prospects are. This is just a matter of conducting initial research and actually trying to build a prototype, which will inform you whether the fully-realised product is truly feasible. * **Viability–** the product's ability to generate sustainable financial returns. Without financial viability, the business supporting the product cannot endure, even if the product is highly appealing to users and technically achievable. Here, you need to look at your unit economics, development costs and other expenses to determine the viability of your solution. \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ Hope you enjoyed reading this; let me know your honest thoughts in the comments and I'll try to improve how I interview founders based on those!