Product sense

Product sense is the intuitive ability to understand what makes a product good. It encompasses user empathy, design taste, and judgment about feature decisions - the capacity to look at a product and understand what's working, what's not, and why. Product sense is what allows someone to evaluate whether a feature will succeed before it ships, to identify friction in user flows, and to know when something feels right or wrong.

Why it matters

Data can tell you what's happening; product sense helps you understand why and what to do about it. Analytics might show drop-off at a particular screen, but product sense helps you feel why users are abandoning and what would make them stay.

Strong product sense enables:

Better decisions. When data is incomplete or unavailable, product sense provides direction.

Faster iteration. Teams with strong product sense don't need to test every micro-decision; they can make good calls and move forward.

Quality bar maintenance. Product sense establishes what "good" looks like, preventing mediocre work from shipping.

User advocacy. People with product sense represent user interests even when users aren't in the room.

Components of product sense

Product sense comprises several overlapping capabilities.

User empathy is the ability to understand users deeply - their needs, motivations, contexts, and emotions. It's not just knowing what users want but understanding why they want it and how they experience the product.

Taste is the aesthetic judgment about what's good. It includes design sensibility, interaction intuition, and the ability to recognize quality. Taste helps distinguish between "this works" and "this is excellent."

Problem framing is the ability to understand problems correctly. Product sense helps identify when the stated problem isn't the real problem and when solutions address symptoms rather than causes.

Trade-off evaluation weighs competing considerations effectively. Most product decisions involve trade-offs; product sense helps make these choices well.

Pattern recognition draws on experience to recognize familiar situations and apply relevant lessons. Having seen many products succeed and fail provides intuition about what works.

Developing product sense

Product sense isn't innate talent; it develops through experience and deliberate practice.

Use lots of products. Exposure to many products - good and bad, in your space and outside it - builds pattern recognition and taste. Pay attention to what works and why.

Observe users. Nothing builds empathy like watching real users interact with products. User research, support conversations, and usage observation all develop understanding.

Practice articulating judgment. When you have a reaction to a product, try to explain why. What specifically is good or bad? The discipline of articulation refines intuition.

Study decisions and outcomes. When products succeed or fail, analyze why. What did the team decide? What alternatives existed? What would you have done?

Get feedback on your judgment. Share your product opinions and see how they hold up. Were your predictions right? What did you miss?

Build things. Making products teaches lessons that observation can't. The experience of shipping and seeing user response develops sense rapidly.

Product sense in hiring

Companies often assess product sense in PM interviews through exercises like:

Product critique. Evaluate an existing product - what's working, what isn't, what would you change?

Feature design. Given a user problem, propose a solution. Interviewers assess how well candidates understand users, make trade-offs, and think through details.

Prioritization. Given competing opportunities, determine what to build. This reveals judgment about value and impact.

Estimation. Make reasonable guesses about metrics, user behavior, or market size. This shows calibration and reasoning ability.

These exercises don't have right answers; they reveal thinking process and judgment quality.

Product sense pitfalls

Strong product sense can lead to problems if not balanced properly.

Overconfidence dismisses data in favor of intuition. Product sense is valuable but not infallible; data should inform and correct judgment.

Taste imposition applies personal preferences to users who are different. Your taste isn't universal; user research keeps product sense grounded.

Anchoring on first instincts resists updating views when evidence suggests otherwise. Product sense should remain open to new information.

Neglecting deliberate analysis relies too heavily on gut feel. Intuition is faster but not always more accurate than structured evaluation.

Product sense and data

Product sense and data aren't opposites; they're complements.

Product sense generates hypotheses about what's happening and what to try. "Users seem confused by this flow" is a product sense observation that can be tested with data.

Data validates or refutes intuitions. Sometimes product sense is right; sometimes data reveals that intuition was wrong.

Data without sense is directionless. Knowing that conversion is 3% doesn't tell you why or what to do. Product sense provides interpretation.

Sense without data is uncalibrated. Intuitions need feedback. Data provides the reality check that improves judgment over time.

Product sense and customer feedback

Customer feedback is a product sense input. What users say about the product - their praise, complaints, and requests - provides raw material for developing and applying product sense.

Tools like Klero help product people develop sense by exposing them to high-volume customer feedback, revealing patterns about what users value, where they struggle, and what they wish the product did differently.