Subscribe
Sign in
How do you validate your problem idea?
What's your best practice to check the customer problem?
I usually take into in depth interview first
33
Replies
@nickanisimov I seee, yes quite difficult to find the honest one.
What will you do to find someone who will honest give the feedback?
or do you have minimum correspondent?
@andrewdietekoki could you spill some part of your experience during validate the problem?
Asking on Reddit for tech product is quite helpful!
For truly groundbreaking innovations, people don't imagine they need it and it's more complicated to assess. I doubt Apple conducted interviews with people when they released their first iPhone.
@vladislavs_sprengels aah true, that end to end capturing product validate.
do you usually do market share and market size analysis thoo?
@ammanahalfian I do! It's not the easiest place to be as a brand and I'm still getting used to rules of engagement, but it's incredibly good for real, honest feedback
The best way to test a client's problem is to meet it as a client, using your application is an important part.
Consider using AI tools like Checkmyidea-ia and Validatorai to validate your idea effectively. These tools can provide you with comprehensive analysis and insights, allowing you to evaluate market potential, understand customer needs, and refine your idea accordingly. Unlock the power of AI to make data-driven decisions for your idea's success!
Validating your problem idea can be done through market research, user surveys, and prototyping - don't forget to test, iterate, and gather feedback along the way! 🚀
@butler99_p wow, that's the whole journey validate problem idea.
What do you think the most difficult one?
What I find problemanting with problem validation is that, in many cases, the problem isn't the problem at hand. It is already a result of a deeper issue.
Firstly I'd validate if the problem exists in the fist place by talking to others and see if they experience it. The 5 why's is a good way to dive in deeper.
Secondly I'd create assumptions and validate if the problem is a real problem or not. Build measure learn principles are useful
talk to potential users. never build anything even a small MVP without validating the idea first.
problem validation, a dance of curiosity, empathy and insight. it's less about confirming our initial hunch, more about exploring the reality of the people we hope to serve.
deep-dive interviews? they're great. but let's not stop there. observe behaviors, they often speak louder than words. dive into their environment, their routines. what's frustrating? what's delightful?
also, let's not forget the beauty of iteration. small experiments to test assumptions can yield profound insights. launch prototypes, seek feedback, refine. it's a dynamic, evolving process.
so while validating, let's embrace uncertainty, celebrate learning and stay open to being wrong. because every step taken, every insight gleaned, it's all part of our journey to create something truly meaningful.
One of the most effective ways I found to validate or check users' problems is to monitor the journey while using your product. I recently integrated Hotjar into a product I'm working on. Using their video recording tool I could see first-hand the user's journey, what issues they had while using your product, etc.
Opportunities can be:
- Identifying user's pain points
- Improvements needed
- Validate some of your hypotheses
- Learn user behavior and more
This is asides from having sessions with customers and collecting feedback.
We hit the pavement and got into deep convos with potential users. Also did some good old fashioned surveying and beta testing.
Gemoo