- Learn more about your hypothesis and assumptions around your solution’s fit to your target audience and problem space.
- Build products that have product/market fit by pivoting or adapting learnings into development of the product.
Early Solution Validation: Once you’ve clearly defined your problem and you know what you are trying to solve, for who and have an idea of how, it is time to start testing the how. There are many ways to test your solution early on, we’ve talked earlier about prototypes and this will take you through how to do solution validation with a prototype.
What you wish to test around your solution. What about the how do you have questions about? What do you want to understand more about? Where did you make assumptions you are unsure of? Write down your questions and come up with a prototype that can test those questions.
Recruit people to test the prototype on. Ideally recruit for people who have the problem you are solving for. But especially in the early days, just getting people to try your solution and see if it works will be helpful. See our recruiting guide for more information.
Let testers know this is a prototype, not a finished product. The goal is not to test them but to test the prototype. Present your prototype to users. You can frame the task, but avoid guiding them. Think out-loud testing is extremely useful in prototype evaluation, so ask users to voice everything they think as they go through your prototype. They may need reminding, so ask often “what are you thinking right now?”. Observe where they have problems and why they have problems. Same rules as for general interviews apply.
5. LEARN AND REPEAT
As your product advances in development you can also advance the prototype techniques you are using and more specifically target the people you test with.
Create a concise summary document that is useful to you and can also be used to keep stakeholders up to date.