Here’s a scenario you might be familiar with. Say you’re starting a new role as a PM in a startup company (congrats!). You find that the startup has created a robust product with many different features and capabilities. Trying to gain some clarity and focus you ask: “which of those features are most/least used?”. Turns out, nobody knows. So you implement basic analytics mechanisms, wait for a week or two and then come back to the team equipped with a bunch of fancy graphs.
hey thanks for publishing this on hacker noon, @sefiK. I really wish I could’ve copied this quote to a post-it note in my office yeeears ago:
> “What assumptions did we have when built this feature, and how do those assumptions fair in light of our current usage data?”