All product initiatives are experiments. We will never be 100% certain of success.
But one way to guarantee failure (and not the kind where you learn something), is with a poorly defined or validated problem statement. Or none at all.
I created problems.design to share problems, frustrations, aspirations, hacks, needs and use-cases that I seee out in the wild. As much as I can, I look for solution agnostic statements. Why?
The solution is your job.