Data is part of a Minimum Viable Prototype
It's good business practice, not "nice to have"
"We need to do so much in order to pivot/get started!"
Do not overcomplicate structuring or getting started with building your product.
There are some product-led motions that should be good business practice in any case. This goes for sales-led, product-led, and marketing-led... Anything!
Start measuring and leveraging your usage data. Change what you consider a "Minimum Viable Prototype"
Even if you go in the future into a sales-led distribution, it never hurts to have proper data coverage of what happens in your product.
Measuring, surfacing and leveraging data should be a key requirement for anything you ship. Including MVPs.
We used to say "Let's ship an MVP and see what happens, we can add tracking later". Turns out, if you don't measure anything about that MVP you cannot in fact *see* what happens.
Gathering: Make data gathering on a qualitative and quantitative level a requirement before anything ships. Events to track need to be in place before launch. Measure especially what you assume will change.
Surfacing: How do we see the impact of our change fast after it has launched? Dashboards? Custom queries?
Implementing proper data tracking and surfacing it in an almost mature product is a pain. It's expensive and it's another excuse once you slowly drifted into a sales-led distribution to never go back.
Get your data in order. No matter what path you go. It's not a product-led growth thing.
It's a good business practice thing.
#productledgrowth #productmanagement #growth #entrepreneur
Thanks for reading Leah’s ProducTea Newsletter! Subscribe for free to receive new posts and support my work.
I am glad to be able to say we are adding tracking into things we add. Not across 100% of features but this is an ongoing investment. One item that kind of helped was including requirements for tracking as a part of definition of ready and then definition of done.