Product Sense Is a Practice, Not a Gift You're Born With

Somebody on your team has it. They glance at a mockup and say "users will bounce on step three," and three weeks later the funnel data agrees. You assume they were born with product sense, that they got a gift you missed. They weren't, and they didn't. Product sense is a practice, not a gift — a set of habits anyone can run on purpose, and the people who seem to have it are just the ones who've been running them longer.

The word makes it sound like a sixth sense, some mystical organ for taste. That framing is convenient for the people who have it and quietly cruel to everyone who doesn't. It tells a capable PM that the thing standing between them and great work is genetic. It isn't. What you're watching when someone "has product sense" is fast pattern recognition built from a thousand small reps you didn't see them do.

What product sense actually is

The clearest definition I've found comes from Jules Walter, a longtime PM at Slack and YouTube: product sense is "the skill of consistently being able to craft products (or make changes to existing products) that have the intended impact on their users." Notice the word skill. Notice consistently. This is not about one inspired idea. It's about being reliably right more often than chance, and that reliability is the tell that something repeatable is going on underneath.

Jackie Bavaro and Gayle Laakmann McDowell make the mechanism explicit in Cracking the PM Career. They compare expert PMs to chess grandmasters: a grandmaster doesn't see scattered pieces, they see a familiar position. Experienced PMs don't see novel problems, they see variations of patterns they've met before, and their advice is to "focus on developing your mental representations around products, businesses, and people." Great product managers, they argue, are "those who reliably ship great products" — and doing that doesn't require "being a creative genius." It requires a stocked library of patterns. You build that library the same way the grandmaster does: with reps.

So here is the practice. Four habits. None of them are clever. All of them work if you actually do them, which is the catch.

Use products deeply, then critique them

Most people use products. They don't study them. The single fastest way to build product sense is to take something you already touch every day and ask why it is the way it is.

Julie Zhuo, who ran product design for the Facebook app for over a decade, wrote the canonical piece on this. Her line is blunt: "There is no shortcut to developing better product instincts besides keen and close observation," and elsewhere she's direct that "product design isn't some innate skill one is born with." The method is a critique, and you can run it on anything. Open an app you've never seen. Watch your own first thirty seconds. Where did you hesitate? What did the onboarding assume you already knew? Where did it ask for something before it had earned the right to ask?

Then go one level deeper than the reaction: name the decision behind it. That confirmation modal that annoyed you — someone shipped it on purpose, probably to cut a support-ticket category. The empty state that taught you what to do next — someone fought for that against a deadline. When you can reconstruct the decision, you're no longer reacting to products, you're reading them. Do this for an hour a week on real products and you'll out-pace a year of passive use.

Predict outcomes, then check the tape

Here's the habit that separates people who feel like they have product sense from people who actually do: they keep score.

Before a launch, write down what you think will happen. Not vaguely — specifically. "Activation goes up 4 points, retention is flat, support tickets about billing drop by a third." Date it. Then when the numbers land, go back and read what you wrote. The gap between your prediction and reality is the most valuable data you will ever generate about your own judgment, because it's the only data that's actually about you.

Almost nobody does this, which is exactly why it works. Unchecked intuition doesn't improve; it just gets more confident. A prediction you wrote down and got wrong is a correction you can't argue with. Six months of dated predictions will teach you more about where your instincts are sharp and where they're systematically off than any framework will. This is the deliberate-practice loop — guess, check, adjust — applied to judgment instead of free throws.

Study why real decisions were made

Patterns compound faster when you borrow other people's. Walter's advice here is to "learn from great product thinkers" — sit in their product reviews, take notes, and find the patterns in their feedback. The point isn't to copy their answers. It's to copy their questions. The PM with sense isn't asking "do I like this?" They're asking: who is this for, what's the goal, what did we trade away to get here, and what would have to be true for this to work?

When a decision lands near you — a pricing change, a feature cut, a redesign — don't just note what was decided. Chase down why. Ask the person who made the call what they were optimizing for and what they considered and killed. The killed options are where the sense lives. Anyone can defend the thing that shipped; judgment is in understanding the three things that didn't and why. This is also the cheapest senior-PM mentorship available: most people will happily explain their reasoning if you ask with genuine curiosity instead of a quiz.

Talk to users until their words live in your head

The last habit is the one with no substitute. You cannot reason your way to what people want from inside a conference room. Zhuo's whole approach starts with watching how people actually experience things, and Walter puts user observation first: spend a few sessions a month watching people use products, paying attention to the micro-expressions — the confusion, the hesitation, the small spark of delight.

Do enough of this and something shifts. You stop guessing what users think and start hearing them. In a design review, an actual customer's voice shows up in your head and says "I'd never find that button." That voice is product sense. It's not intuition in the magical sense — it's a compressed memory of fifty real conversations, retrieving the right one at the right moment. The PMs who seem psychic about users are just the ones who've logged the hours.

The part nobody wants to hear

If you feel like you don't have product sense, the diagnosis is almost never that you lack the gift. It's that you haven't been running the practice. You've been using products without critiquing them, shipping without predicting, accepting decisions without interrogating them, and reading user research summaries instead of watching the sessions. All four are fixable this week.

The reason product sense looks like talent is that the reps are invisible and the results are loud. You see the grandmaster make the move; you don't see the ten thousand games. Start logging your games. Critique one product, write one dated prediction, ask one "why did we decide that," watch one user session. None of it requires permission, and all of it compounds. The gift was never the point. The practice always was.