You're focusing on the process ("data-driven decision making") and not on what you actually want to accomplish (a better product). You should try it the other way around.
Start by thinking about your vision for the product. Where do you want it to go? How do you want people/customers to think of it?
Then start thinking about how you might recognize whether your vision has actually happened: the degree to which the product has arrived at where you want it to be, how people think of it, what characteristics it needs to have, etc. Then start thinking about what sort of data you would want to collect in order to recognize all this, tempered by what sort of data you actually can collect.
Then go out and collect it. In other words, devise a data-collection strategy and implement it. That implementation should be your outcome, and your Key Results should relate to the successful collection of data.
Once you have enough data, and given that you know exactly how each piece of data relates to the vision/strategy, a dashboard/report becomes easy to design. Data-driven decision-making follows naturally.