I build products that actually ship.
Not wireframes that collect dust. Not decks without decisions. Real features, real users, real iteration.

Origin

I discovered product management through my interest in business, marketing, and technology. After completing my 12th in Commerce, I pursued BCA to strengthen my technical understanding and explore the intersection of business and tech. While exploring career paths, I came across the role of a Product Manager and became curious about how products are built, scaled, and improved. I started learning through YouTube, online resources, and case studies, which introduced me to concepts like user research, PRDs, GTM strategy, and product thinking.
I discovered product management through my interest in business, marketing, and technology. After completing my 12th in Commerce, I pursued BCA to strengthen my technical understanding and explore the intersection of business and tech. While exploring career paths, I came across the role of a Product Manager and became curious about how products are built, scaled, and improved. I started learning through YouTube, online resources, and case studies, which introduced me to concepts like user research, PRDs, GTM strategy, and product thinking.

How I think

Outcome over output. I don't measure success by features shipped, but by behavior changed. Every roadmap item answers: “what metric moves?”
User stories are hypotheses. I've interviewed dozens of users — not to validate my ego, but to find where reality breaks assumptions. Then I prototype and test in days, not months.
Data + intuition, not politics.I balanced growth experiments and platform bets. I use analytics, but I also know when to trust pattern recognition.
Write to think. Investor-grade PRDs, product specs, post-mortems — clarity in writing forces clarity in strategy. If it's ambiguous in a doc, it will fail in execution.

Where I've applied this

One belief

“Great product managers don't wait for permission. They frame the problem, align stakeholders, and ship something learnable — even if it's small.”
I don't need a formal title to think like a PM. I've already been making those calls: prioritizing features, saying no to distractions, and translating user pain into executable roadmaps.
Or reach out for a portfolio walkthrough / product conversation.