Disclaimer - I'm not a ridiculously successful expert, but below is what I've gleaned from my experience: I feel the question isn't where a tool/idea originate

Disclaimer - I'm not a ridiculously successful expert, but below is what I've gleaned from my experience: I feel the question isn't where a tool/idea originates.. it should be, does this tool/idea provide effective, appropriately-priced, accessible, problem-oriented features that target market-derived problems? Also, there are problems seeking solutions, and solutions seeking problems. It's important to know which case you're looking at. It can be more difficult to be a solution seeking a problem. I have been both an engineer and a product manager. I built internal tools, and tools for sale externally. When I learned more about formal product management, it made so much more sense where to start. This is an oversimplification but, if you're doing fundamental R&D or internal tools, and not trying to yet build a publicly facing business, then focus on the purpose you are trying to unlock. If you're trying to build a publicly facing, sustainable business, focus on identifying a market problem, and building problem-oriented features to address them, making those solutions available and visible to those who need them, and acquiring/serving customers. The beauty of some of this is that, these days it can be possible in some cases to focus on identifying something that is a market problem, make a minimal version of the solution visible with low investment, find out if this is something that makes sense to continue to build, and then iterate rapidly. A lot of the above is regurgitated "best practices in product management", to be fair, but overall I've found it really helpful guidance.