Hi all! I wanted to share ten questions I ask during product/feature discovery before actually starting to build. Validation is key so you don't waste your time!
1. What problem are you currently facing in relation to [idea domain]?
This question is straightforward but it's the cornerstone of your interview. It's essential to understand the problem from the user's perspective. It allows you to explore the nuances and implications of the issue your idea is aiming to solve.
2. How often do you encounter this problem?
Frequency is an important factor in determining the severity of the problem. If it's something they encounter daily, it's likely to be a more pressing issue than if it happens once a month. People are more willing to pay to solve problems that they deal with frequently.
3. Have you ever paid money to try and solve this problem?
Most “would you pay for this” solutions end up getting wishy washy answers but this question helps you to better gauge the monetary value users place on a solution. If they've paid for a solution in the past, it's a strong indication that they might be willing to pay for a better one in the future.
4. How are you currently solving that problem?
The answer to this question gives you insights into your competition and the alternatives users have available. It also helps you understand the current behavior and habits of your potential users. You’ll be shocked at how many users answer this question with a manual / inefficient process.
5. What do you like and dislike about that solution?
This question gives you insights into the pros and cons of the current solutions from the user's perspective. These can be translated into features and benefits of your own product and can expose additional layers to the problem and pain point.
6. If you could wave a magic wand and have the perfect solution to your problem, what would it look like?
This is your opportunity to dream with your user. It’s always good to take user feature requests with a grain of salt but at the very least understanding how users envision a solution to their problem can add valuable context around how they think about the problem itself.
7. *After explaining how you’re approaching the problem* Do you think this would adequately solve the problem? Would you use a product like this?
Here, you are testing the waters with your solution. Their feedback is critical in shaping the direction of your product and understanding if the user would find it valuable. It also validates if your solution resonates with their needs.
8. Can you think of any potential drawbacks or challenges you might face when using our proposed product?
Understanding potential challenges or barriers to adoption helps you anticipate and plan for them in your product strategy, marketing, etc..
9. Would you be willing to try our solution when it’s ready, and provide feedback?
This question is crucial for building a list of potential beta testers. It also demonstrates the user's interest and engagement with your proposed solution. It’s worth noting that if people aren’t willing to sign up for a free beta access waitlist them it’s likely that either the problem isn’t as painful as you thought or your solution is missing the mark.
10. Do you know anyone else that experiences this problem? Would you mind introducing me so I can talk to them?
Growing your interview pool through user referrals can give you a wider perspective. It also helps validate if the problem is widespread enough to warrant a solution. Additionally, if you’re asking question 9 this can help turn these people into beta users in the future.
If you found this helpful I write snippets like this every week at https://www.growthinclined.com/. Thanks for taking the time to read it!
1. What problem are you currently facing in relation to [idea domain]?
This question is straightforward but it's the cornerstone of your interview. It's essential to understand the problem from the user's perspective. It allows you to explore the nuances and implications of the issue your idea is aiming to solve.
2. How often do you encounter this problem?
Frequency is an important factor in determining the severity of the problem. If it's something they encounter daily, it's likely to be a more pressing issue than if it happens once a month. People are more willing to pay to solve problems that they deal with frequently.
3. Have you ever paid money to try and solve this problem?
Most “would you pay for this” solutions end up getting wishy washy answers but this question helps you to better gauge the monetary value users place on a solution. If they've paid for a solution in the past, it's a strong indication that they might be willing to pay for a better one in the future.
4. How are you currently solving that problem?
The answer to this question gives you insights into your competition and the alternatives users have available. It also helps you understand the current behavior and habits of your potential users. You’ll be shocked at how many users answer this question with a manual / inefficient process.
5. What do you like and dislike about that solution?
This question gives you insights into the pros and cons of the current solutions from the user's perspective. These can be translated into features and benefits of your own product and can expose additional layers to the problem and pain point.
6. If you could wave a magic wand and have the perfect solution to your problem, what would it look like?
This is your opportunity to dream with your user. It’s always good to take user feature requests with a grain of salt but at the very least understanding how users envision a solution to their problem can add valuable context around how they think about the problem itself.
7. *After explaining how you’re approaching the problem* Do you think this would adequately solve the problem? Would you use a product like this?
Here, you are testing the waters with your solution. Their feedback is critical in shaping the direction of your product and understanding if the user would find it valuable. It also validates if your solution resonates with their needs.
8. Can you think of any potential drawbacks or challenges you might face when using our proposed product?
Understanding potential challenges or barriers to adoption helps you anticipate and plan for them in your product strategy, marketing, etc..
9. Would you be willing to try our solution when it’s ready, and provide feedback?
This question is crucial for building a list of potential beta testers. It also demonstrates the user's interest and engagement with your proposed solution. It’s worth noting that if people aren’t willing to sign up for a free beta access waitlist them it’s likely that either the problem isn’t as painful as you thought or your solution is missing the mark.
10. Do you know anyone else that experiences this problem? Would you mind introducing me so I can talk to them?
Growing your interview pool through user referrals can give you a wider perspective. It also helps validate if the problem is widespread enough to warrant a solution. Additionally, if you’re asking question 9 this can help turn these people into beta users in the future.
If you found this helpful I write snippets like this every week at https://www.growthinclined.com/. Thanks for taking the time to read it!