What Is Product Sense (And Can You Actually Learn It)?

Some builders ship a feature and users just get it. No manual, no support ticket, no confusion. Other builders ship the same kind of feature and people get stuck, complain, or quietly disappear.

The difference is rarely raw coding skill. It is something quieter and harder to name: product sense. And the good news, which surprises most people, is that you can learn it on purpose.

Why this matters

You can be a brilliant engineer and still build things nobody wants. You can write clean code, ship fast, and hit every deadline, while users churn and you cannot figure out why.

Product sense is the skill that decides whether your effort lands. It is the difference between a feature that quietly does its job and one that generates a pile of confused support tickets. For founders, it is the difference between building the right thing and building the wrong thing with great conviction.

Master it, and your work starts to matter in a way that effort alone never guarantees.

What product sense actually means

Product sense is an intuition for what to build and why it will matter to real people.

More precisely, it is the skill of consistently making product decisions, whether that is a new feature, a small tweak, or even the wording on a button, that have the intended positive effect on the people who use what you build.

The product writer Jules Walter put it crisply: product sense is “the skill of consistently being able to craft products that have the intended impact on their users.”

Notice the word consistently. Anyone can get lucky once. Product sense is the difference between a good guess and a reliable instinct.

The key idea: Product sense is not “having good ideas.” It is reliably knowing which idea will actually help a real person, and which polished-looking idea will not.

The two halves: empathy and judgment

Product sense is built from two skills that only work when they work together.

1. Empathy (the discovery half)

This is understanding people’s real needs, their situation, their constraints, and, crucially, their feelings.

What is the user actually trying to get done? Are they in a rush or relaxed? Anxious, bored, frustrated, or delighted? Empathy is how you discover the true problem, which is often hidden behind what people say they want.

2. Judgment (the decision half)

This is deciding what is worth building, including the courage to say no, and deciding how it should feel.

It is prioritization plus craft: choosing the few things that matter and getting the details right.

You need both. Empathy without judgment means you understand your users deeply, then drown them in a cluttered, unfocused product. Judgment without empathy means you build something elegant and beautifully crafted that solves a problem nobody actually has.

An analogy: Empathy is the doctor listening carefully to where it hurts and when. Judgment is the doctor choosing the one right treatment instead of prescribing everything in the cabinet. A great doctor needs both. So does a great builder.

What it looks like in practice

The clearest way to see product sense is to watch how decisions change with it and without it.

• Without it, you start from the technology: “We built this capability, now where can we use it?” With it, you start from the user’s situation and the job they need done.
• Without it, you add options to feel “complete.” With it, you subtract choices to make the right path obvious.
• Without it, you ask “Would you like feature X?” and believe the polite yes. With it, you watch what users actually do and struggle with.
• Without it, success means shipping. With it, success means impact on real people.
• Without it, “Saved” messages and empty screens feel like optional polish. With it, they are core parts of the product.

Steve Jobs captured this reversal at Apple’s 1997 developer conference. Answering a hostile question, he said: “You’ve got to start with the customer experience and work backwards to the technology, not the other way around.”

He even admitted he had made the opposite mistake “more than anybody else in this room… and I’ve got the scar tissue to prove it.” His point was not that technology is unimportant. It is that the arrow must point from “what benefit can we give the customer?” toward the technology, never the reverse.

Why engineers and founders especially need it

Engineers are trained to start from the architecture and the technology, which is exactly the trap Jobs named. Product sense reverses the arrow: experience first, technology in service of it.

Founders face a different trap: polite lies. When you ask friends, family, or early users about your idea, they encourage you instead of telling the truth.

Rob Fitzpatrick’s book The Mom Test is named for exactly this. Good questions get useful answers “even from your mom,” who wants to protect your feelings. His core rule: talk about their life, not your idea. Ask about specific things people have actually done in the past, not their opinion of your hypothetical future. Talk less, listen more, and never pitch.

Founders without product sense mistake compliments for proof.

The most common mistake: Asking “Would you use this?” The honest answer is always a polite “sure.” Ask instead, “Walk me through the last time you had this problem. What did you do?” The past is true. The future is flattery.

Common misconceptions

Myth: Product sense is a gift you are born with.

The word “sense” misleads people. It sounds innate, like a sharp sense of smell. It is not.

Marty Cagan of Silicon Valley Product Group argues that strong product sense is better named deep product knowledge: the result of immersing yourself in one product space, its users, its data, its industry, its competitors, its technology. “There is no substitute for doing the homework,” he writes. Everyone who has strong product sense earned it, even if they no longer notice the effort that produced it.

Myth: More features means a better product.

Two well-known design principles say otherwise. Hick’s Law holds that decision time grows with the number of choices, so subtracting options is itself a product-sense move. Jakob’s Law notes that users spend most of their time on other apps and sites, so they expect yours to behave the same way. Familiarity makes hard things feel easy, so do not reinvent conventions without a reason.

Myth: Good design is the decoration you add at the end.

The opposite is true. The best design removes the need for explanation entirely, which brings us to the heart of the matter.

The real payoff: making hard things obvious

Here is the visible result of product sense and empathy working together: something genuinely hard, hard to build or hard for the user, ends up feeling effortless and self-evident. The user just knows what to do.

Don Norman, in The Design of Everyday Things, gives us the vocabulary. An affordance is an action an object makes possible, like a door that can be pushed or pulled. A signifier is a visible cue telling you which action to take, like a flat plate that says push or a rounded handle that says pull. When signifiers are good, you act correctly without thinking.

The villain of his book is the “Norman door”: a door with a pull-handle on a side you must push, so someone tapes a “PUSH” sign on it. That label is the tell-tale sign of failed design. Good design removes the need for the label by making the right action obvious.

A real example: In a print shop tool used by non-technical owners, a checkout that needs a tooltip explaining each field is a Norman door. The fix is not a better tooltip. It is a layout, order, and wording so plain that the next step is obvious without one.

The milkshake that explains everything

The deepest empathy idea here comes from Harvard’s Clayton Christensen, who popularized Jobs to Be Done. The thesis: people don’t simply buy products, they “hire” them to do a job in their life. What you should study is the progress the customer is trying to make, not their age or demographics.

The famous milkshake story shows why this matters so much.

A fast-food chain wanted to sell more milkshakes. It surveyed customers, “improved” the shake to match the feedback, and sales did not move. Then a researcher stood in a restaurant for about 18 hours, logging every shake sold: the time, dine-in or to-go, what else was bought, alone or with company.

The finding: nearly half of all shakes sold between 6:30 and 8:30 a.m., bought alone, as the only item, by people driving off.

So they asked those buyers what job they were hiring the shake to do. The answer: a long, boring commute, one free hand needing something to do, not hungry yet but soon. A thick shake takes about 20 minutes to drink and stays filling. It beat the alternatives. Bananas vanished too fast. Bagels were dry and needed two hands. Donuts were messy.

The shake’s real competitors were bananas, bagels, donuts, and boredom, not other milkshakes. The right fixes, like making it thicker and moving it to an easy-grab spot for the morning rush, were invisible until someone uncovered the real job and context.

The key idea: Empathy means finding the real job and context. That morning commute stays hidden if you only study your product or your customers’ demographics.

How to grow your product sense on purpose

Product sense comes from a simple loop: exposure (deeply using products and watching real users) feeding feedback (critiques, shipping, and seeing real outcomes). Repeat, and your instinct sharpens. Here is how to run that loop deliberately.

1. Watch real users a few times a month. Sit beside someone using your product. Note the exact moment they hesitate, frown, or smile. Say nothing. Just observe.
2. Deconstruct products you love and hate. Use them slowly and mark the precise instant of friction or delight. Ask why it happened.
3. Ask about behavior, not opinions. Replace “Would you use this?” with “Tell me about the last time you faced this problem.” Let people describe what they actually did.
4. Subtract before you add. For every feature you consider, ask what you could remove to make the right path more obvious.
5. Sit in on product critiques. Listen to how strong thinkers frame a decision and what tradeoffs they weigh. Borrow their questions.
6. Hunt for the Norman doors in your own work. Anywhere you need a tooltip, a help link, or an explainer, treat it as a clue that the design itself can be made clearer.

Conclusion

If you remember one thing, remember this: product sense is not a gift, it is a habit of curiosity you can build. It is the reliable instinct for what to build and why it will matter, measured by real impact on real people rather than by whether you shipped.

The clearest sign you are getting it right is when something hard starts to feel obvious, when the “PUSH” label is no longer needed because the door simply makes sense.

But knowing what to build is only half the story. The harder, more human question is how you uncover what people truly need when they often cannot tell you themselves. That is where empathy stops being a buzzword and becomes a craft, and it is exactly where we go next.