How to Test a Technology Solution

Product testing is really about knowing the problem, not deploying a piece of technology because it's cool or just for the sake of it. And then knowing what you want day two to be with this technology in place and targeting that as the success. I imagine throughout that process, or even maybe absent of that process, there are companies who will try to go down the product testing route and not do it successfully. So from your experience, where along the product testing kind of journey do teams go wrong? What advice do you have for them on kind of maybe how to avoid either common pitfalls or things that could come up that are good to know early on?"