Most people confuse Product Sense with product management. They're not the same thing. Product management is a job. Product Sense is a way of seeing — and you can develop it whether you're a PM, an engineer, a designer, or someone who's never worked in tech at all.
I've met PMs with five years of experience who have almost no Product Sense. And I've met fresh graduates who walk into a product review and immediately ask the question that cuts to the core of the problem. The difference isn't experience. It's a habit of attention that one person has cultivated and the other hasn't.
The good news is that it's trainable. Here's how I think about building it deliberately.
Step 1 — Become a dissatisfied user
Where does it slow you down? What do you tap on by habit, even though it doesn't quite do what you want? What would you remove? Don't read about it — use it, feel the friction. Write three things down. Not features — feelings. "This feels slow." "I never know where I am." "I always misread this button."
Most people use products on autopilot. Product Sense starts when you switch off autopilot and start noticing. You're training your brain to register friction instead of ignoring it.
Step 2 — Ask "why does this exist?" not "what does this do?"
Not what the feature does. Why it exists. Instagram's Close Friends list — what was the problem? YouTube's autoplay — what user behaviour were they trying to change? LinkedIn's "People Also Viewed" — who does this actually serve? Asking "why does this exist" forces you into the problem space. That's exactly where Product Sense lives.
Step 3 — Observe real people, not personas
Watch your parents use Google Pay. Watch a friend book a flight. Watch a child use YouTube. You will immediately see things you've never noticed. Where they pause. What confuses them. What they do differently from you. Real observation destroys assumptions faster than any amount of data analysis. Do this once a week if you can.
Step 4 — Develop taste by consuming deliberately
A hotel check-in that was surprisingly smooth. A government form that was actually clear. A restaurant menu that made ordering easy. Product Sense is built from a library of moments — both good and bad — that you've paid attention to. The library only grows if you're actively adding to it. Most people let these moments pass. Don't.
Step 5 — Practice articulating the trade-off
Not "they added a dark mode." But: "they chose to invest engineering time in a feature that deepens engagement for existing power users, at the cost of simplicity for new ones." Every product decision is a trade-off. The moment you can see the trade-off clearly, you're thinking in product. This is the core of Product Sense — not knowing what to build, but knowing what you're giving up when you build it.
The honest thing about Product Sense
It takes time. There's no shortcut. But the single fastest accelerant I've seen is this: stay in the problem longer than feels comfortable. Most people jump to solutions — it feels productive, it feels smart. Sitting with a problem, turning it over, asking why it exists, who it really affects, what would change if it disappeared — that is the work. Everything else follows from that.
You don't develop Product Sense by reading about products. You develop it by paying a different kind of attention to the world you already live in.