How I Fell in Love with Problem Solving (Before I Even Knew What a PM Was)

Before I knew what a “Product Manager” did, I was already acting like one — without realizing it.

No fancy frameworks. No Jira tickets. Just an itch I couldn’t ignore: “There has to be a better way to do this.”

I didn’t know it then, but that quiet frustration — that constant urge to fix, improve, and make things smoother — was my earliest sign of falling in love with problem solving.

🧩 The Early Signs of a Product Mindset

Looking back, it started with small, everyday moments.

In college, I remember organizing a campus event where the registration process was chaos — long queues, messy spreadsheets, and missing names. Everyone complained, but I couldn’t stop thinking about how we could fix it.

So I built a quick Google Form, automated confirmations with email scripts, and created a simple dashboard to track attendees.

The result? ✅ No queues. ✅ No confusion. ✅ Everyone thought I’d done magic — but honestly, all I did was solve a problem that bothered me.

At the time, I didn’t realize this was product thinking in action. I was just… curious.

🔍 Curiosity Is Where It All Begins

What I’ve learned since is that product management starts long before job titles do.

It begins with curiosity. It begins with noticing friction. It begins with caring enough to ask why something feels harder than it should be.

I used to think problem-solving meant having big, world-changing ideas. But I realized it’s often about small things that make life easier for people — fixing a bottleneck, clarifying an experience, or removing one extra step from a process.

Those small wins build the instinct that every PM needs: to see problems even when others walk past them.

🛠️ From Fixing Things to Understanding People

Over time, my love for problem-solving evolved from systems → to people.

I started asking questions like:

• Why do people behave this way?
• What emotion are they feeling when they abandon this step?
• What would make them stay longer or smile more?

That’s when I realized — every product is a story of human behavior.

You’re not just solving a technical issue; you’re solving someone’s frustration. You’re not optimizing a flow; you’re easing a human need.

And that’s when I knew I didn’t just like fixing things — I loved understanding why things break in the first place.

🚀 The Moment It Clicked: “Wait, This Is a Job?”

I still remember when I first came across the term Product Manager.

As I read the description, it felt strangely familiar:

• Identifying user problems ✅
• Collaborating across teams ✅
• Balancing user needs with business goals ✅
• Building something from 0 to 1 ✅

It hit me — I’d been doing pieces of this all along.

That’s when I knew I wanted to do it intentionally.

Because product management isn’t about being technical. It’s about being relentlessly curious, empathetic, and driven to make things better.

✨ What Falling in Love with Problem Solving Taught Me

If I had to summarize my journey so far, it would be this: You don’t wake up one day as a “problem solver.” You become one — by caring deeply about why things don’t work and imagining how they could.

And sometimes, your career finds you before you even know what to call it.

Today, as an aspiring Product Manager, I don’t just want to solve problems. I want to understand them. I want to listen before I fix. And I want to build things that make life easier, one human problem at a time.

Because the truth is — I didn’t choose product management. Problem solving chose me. 💛