You don't need more data

A pattern I've seen often is teams trying to prove an idea by asking for more data before they build anything.

Data has two fundamental problems in this situation. One is that you can prove or kill a solution with the same exact data. It all depends on how you frame it.

Further, pre-implementation data - like existing user behavior, feedback from similar products - is dramatically less useful than post-implementation data - like actual usage, customer complaints, or bugs after the launch.

That's why a better strategy for the pre-implementation stage is to pick proven ideas you have high conviction for and ship fast. When the product is out there, the real data will guide you to the next best decision.