From Spreadsheets to Shipping: How Data and Growth Made Me a Product Manager

Data taught me to argue with evidence, not opinion

My first job was making messy data answer questions. ImportRange, Query, Index-Match, a lot of SQL, and dashboards that combined ten different sources so product, marketing, and sales could finally see the same picture. It sounds unglamorous, and it was, but it rewired how I make decisions.

Once you've built the dashboard, you stop trusting hunches. You learn that the loudest opinion in the room is rarely the one the data supports, and that a 5% lift you can actually measure beats a "huge impact" nobody can point to. As a PM, I still reach for the data first. I'd rather be corrected by a number early than by a launch later.

Growth taught me that shipping is a habit, not an event

In a growth role you live or die by the loop: try something, measure it, kill what's not working, double down on what is. Reactivating inactive leads, running referral flows, building retention nudges across WhatsApp, email, and app, none of it works on the first try. What works is the speed of the second, third, and tenth try.

That gave me my stubborn bias for shipping. I'd rather put a rough version in front of real users this week than a perfect one next quarter, because the real version teaches me things no plan can. Growth taught me to treat shipping as a habit, and that habit didn't leave when I moved into product.

Product is all of it at once, with a roadmap attached

Data taught me to find the truth in the numbers. Growth taught me to move fast and learn in public. Product is both of those, plus the discipline of choosing what not to build and the patience to align features with where the business actually needs to go.

The thread through all of it is the same instinct: get close to the real problem, prove it with evidence, and ship something that makes a user's day easier. That's the circle of product life, OKRs to roadmaps to execution, and every earlier role was just teaching me a different part of it.

What I'd tell anyone taking the same path

Don't wait for the perfect title to start thinking like a PM. If you're in data, ask what decision your dashboard is meant to change. If you're in growth, treat every experiment as discovery. The skills compound quietly, and one day you look up and realise the spreadsheets, the experiments, and the late-night JSON debugging all added up to a way of building products that's entirely your own.