Every PM video on YouTube says the same thing. Use this framework. Think in this perspective. Apply the 80/20 rule. Build mental models.
I watched all of it. Read all of it. Still didn't know what to actually do on day one.
Nobody tells you that part. So here's what I think actually matters.
You're already doing it
Every morning I book an auto. Uber or Rapido. Both do the same job. But I noticed I was using Rapido more. Not because it was cheaper or faster.
One day I realised — I was saying the OTP from memory. Without looking at my phone.
Rapido doesn't refresh its code like Uber does. Uber gives you a new OTP every ride. Rapido keeps the same one. They even call it a PIN, not an OTP.
At first I thought — is this a bug? Lazy engineering?
Then I stopped and thought about it. If you're booking an auto in the same city, the odds of getting the same driver twice are very low. So why refresh every time? Every refresh is a server call. Every server call is a cost. And for the user — one less thing to look up.
Someone at Rapido made a deliberate decision. A small one. Invisible. And now their PIN lives in my head without any effort.
That moment — that noticing — is product thinking. Not a framework. Not a course. Just asking: why did they do it this way, and what problem does it solve?
The difference is small
You already do this. You just don't call it product thinking.
Every time an app feels slightly annoying — that friction you noticed is a product problem someone missed. Every time you rearrange how you explain something because the first version confused people — product thinking. Every time you find a faster way to do something at work and wonder why nobody did it earlier — product thinking.
The difference between a product manager and everyone else isn't a certificate. It's noticing. And then not letting it go.
Most people feel the friction and scroll past it. Product managers feel the friction and it bugs them until they understand why.
So how do you actually become one
Stop collecting frameworks and start noticing things. Use a product, any product, and ask yourself three questions:
- Why does this work this way?
- What problem were they solving?
- What would I do differently?
Do this enough and you'll start seeing patterns. That's the skill. Everything else — PRDs, user stories, sprint planning, Jira — you'll pick up on the job. Those are tools. The actual skill is the noticing.
I didn't become a PM because I took a course. I became one because I couldn't stop asking why things were built the way they were. The career path was messy — psychology, MBA, business analyst, then PM. But the thread through all of it was the same: I kept noticing things and couldn't shut up about them.
Start here
Pick one app you use daily. Use it tomorrow and pay attention. Find one decision someone made — a button placement, a default setting, a flow that feels faster than it should. Ask why.
That's it. That's the first step. Everything else comes after.