I'm not specifically talking about code quality, but usually that goes hand in hand with the product. An engineer that makes quality code will usually also care about the product quality overall as well. Good code quality makes that quality product maintainable and fun to work in.

That being said, your product's traits are phenotypes of your code design. Its performance characteristics, its capable features, how it scales, everything is intertwined. Involve your developers more in the product planning, don't try to plan it for them and just hand them a spec. I've seen too many "product managers" and officers try to be engineers... That's like a real estate tycoon making blueprints for an architect.

You will probably fail if you want to "do high quality code later" as your product will be shit because it's DNA is trash.

And yes, you are trying to persuade yourself, you should be user #1 and your ultimate fan.

Find a problem you have or recognize, and develop a solution you believe in.

Others can barely even recognize there is a problem in the first place, let alone find the optimal solution.

You can listen to others for minor adjustments after the fact, but your product vision is solely on you.