A little
about me.
I got into product through data. I was the person reading dashboards, watching users drop off at step 3, wondering why no one was doing anything about it. Eventually I realised I wanted to be the one doing something about it.
What pulled me in was the combination: understanding people deeply, finding the real problem underneath the stated one, and then moving fast enough to put something in their hands before the theory gets stale.
I thrive in the messy, cross-functional middle — where engineering wants one thing, business wants another, and the user just wants it to work. That chaos is where I feel most useful.
I think in prototypes, not decks.
When I have an idea, I want to put something in someone's hands as fast as possible. A working thing tells you more in 10 minutes than a slide tells you in an hour. Feedback on something real is the only kind that counts.
When stuck, go back to zero.
My first move on a hard problem is to strip out all the assumptions and start from the most basic question. Then I ask someone with no skin in the game — the most honest feedback almost always comes from outside the building.
Outcomes over outputs. Always.
I'm genuinely not interested in shipping features. I want to change something measurable in a user's life. If I can't point to the difference it made, it wasn't worth building.