What does data-driven product management really mean?
In episode 83 of this podcast my guest Noa Ganot reminded us that the term “data-driven product management” originally meant you weren’t prioritizing what to build simply based your own opinions, out of your own head, or the opinions of your colleagues.
You would use “data” – such as interviews, observations, and surveys – that came from research, especially with customers.
She noted that as our tools have gotten more powerful, our vision has unfortunately gotten narrower, to the point that we think of “data” only as “numbers gained from analytics.”
Doing data-driven product management doesn’t mean you have analytical numbers to justify every decision.
It means you use data to help justify your decisions (because there is never certainty).
- Reply All episodes about Compstat – Part 1, Part 2.
- Value Inequality episodes of this podcast – Part 1, Part 2
- How To Measure Anything, by Douglas Hubbard.
- Analytical prioritization (a conceptual math model) podcast episode.
Don’t forget to subscribe!
If you want to help me out, and more importantly, help other product managers find and enjoy this podcast, please subscribe on your podcast system of choice. And consider giving me a review on iTunes or “starring” the episode on your player. It helps other people find the podcast, and makes me a little happier as well. I might even read your review in an upcoming episode.
If you have comments, questions, or complaints about this episode or the podcast, please leave a comment down below and I’ll get back to you immediately.