What Product Sense Really Is

Some builders ship a feature and users instantly "get it" — no manual, no support ticket, no confusion. Other builders ship the same kind of feature and users get stuck, complain, or quietly walk away. The difference is rarely raw coding skill. It is something quieter and harder to name: product sense. This chapter explains what that phrase means, what it is made of, and why it is the single most valuable skill a software builder can grow.

A plain definition

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 — new features, small changes, the wording of a button — that have the intended positive impact 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 designer Julie Zhuo (former VP of Design at Facebook) describes the underlying habit as plain curiosity: the urge to ask why some products feel great to use and others feel like a chore. A product succeeds because it solves a real problem for real people — and product sense is the muscle that lets you sense, before you ship, whether it will.

The two halves: empathy and judgment

Product sense is built from two skills that must work together.

1. User empathy (the discovery half)

Understanding people's real needs, their situation, their constraints, and — crucially — their feelings. What is the user actually trying to get done? Where are they, in a rush or relaxed? Are they 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 / taste (the decision half)

Deciding what is worth building — including the courage to say no — and deciding how it should feel. This 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 but 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.

With vs. without product sense

Steve Jobs captured this reversal in a famous moment 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 admitted he had made the opposite mistake "more than anybody else in this room… and I've got the scar tissue to prove it." The 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 — 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 (2013) is named for 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 and build the wrong thing with great conviction.

Busting the myth: it is learned, not gifted

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.

This means product sense is a learnable skill. Julie Zhuo, Jules Walter, and Cagan all agree. The formula is simple:

   EXPOSURE                 FEEDBACK
   (use products deeply,    (critiques, shipping,
    watch real users)  -->   seeing real outcomes)
        \                       /
         \                     /
          v                   v
        a sharper sense of what works
          (then repeat the loop)

The guide's central theme: hard things made obvious

Here is the visible result of product sense plus empathy: 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 (1988; revised 2013), gives us the vocabulary. An affordance is an action an object makes possible (a door can be pushed or pulled). A signifier is a visible cue telling you which action to take (a flat plate says push; a rounded handle 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.

Two compiled "laws of UX" (gathered by Jon Yablonski, 2020) reinforce this. Jakob's Law (from Jakob Nielsen) says users spend most of their time on other sites, so they expect yours to work the same way — familiarity makes hard things feel obvious, so don't reinvent conventions without a reason. Hick's Law (Hick & Hyman, 1952) says decision time grows with the number of choices — so subtracting options is itself a product-sense move.

Jobs to Be Done and the milkshake

The deepest empathy idea in this guide comes from Harvard's Clayton Christensen, who popularized Jobs to Be Done (JTBD): people don't simply buy products — they "hire" them to do a job in their life. The thing to study is the progress the customer is trying to make, not their age or demographics.

The famous milkshake story shows why. A fast-food chain wanted to sell more milkshakes. It surveyed customers, "improved" the shake to match the feedback — and sales didn't move. Then a researcher (the work is often credited to Bob Moesta's group) 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. The next morning they asked 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 — and a thick shake takes about 20 minutes to drink and stays filling. It beat the alternatives: bananas vanished too fast, bagels were dry and crumbly and needed two hands, donuts were messy.

The shake's real competitors were bananas, bagels, donuts, and boredom — not other milkshakes. The fixes (make it thicker, add fruit chunks, move it to an easy-grab spot for the morning rush) were invisible until someone uncovered the real job and context.

Key takeaways

• Product sense is the reliable intuition for what to build and why it will matter — judged by real impact on real people, not by shipping.
• It has two halves that must work together: empathy (discover the true need and feeling) and judgment/taste (decide what is worth building and how it should feel).
• It is learned, not gifted — built from a loop of exposure (deep use, watching users) and feedback (critique, shipping, seeing outcomes).
• Engineers must flip the arrow from technology-first to experience-first; founders must beat "polite lies" by asking about behavior, not opinions.
• The visible payoff is the guide's theme: great products make hard things feel obvious — no "PUSH" label required.