[borplk]

> You should work on a product that solves YOUR problem

I think this popular advice is flawed. It's survivorship bias in advice form.

If you happen to have a good profitable problem you go solve it and become successful and then turn around and say "Look! I solved my own problem".

There exist many people whose own problems are terrible for turning into a product for many reasons. They would be better off if they attempted a more practical problem that was not necessarily their own.

I also see founders reverse-engineering their story to mask the fact that they just went after a feasible profitable idea.

For example they create a customer support software (as an example of a crowded competitive field).

But because it's not sexy to not have a dreamy story they manufacture some forced story line like "We were running this small consultancy company and needed customer support software. After trying tens of existing solutions we just weren't happy with their X,Y,Z so we decided to solve our own problem for good!".

[ziikutv]

From the looks of it, OP has a product and they does not know the problem it solves. Anyway you slice that - regardless of how "cliche" solving your own problem is - is a problem.

Edit 2: Addendum to above: Even with the suggestion you've made, that assumes you know the problem BEFORE you have a product. OP has a product.

But yes. OP, if you combine both of these 2 cents, your 4 cents would be: Know the problem before you have a product not the other way around :)

Edit 1: Also, note that there are new set of biases to worry about in the approach you have pointed out; does not make it invalid, but you also have to be careful there.