5 Tips for Developing Your Product Sense

Project Management

Product sense — the intuitive judgment that allows experienced product managers to quickly assess whether a product direction is right, whether a proposed feature will create value, or whether a design decision serves users well — is one of the most valuable and least formally teachable capabilities in the discipline. It develops through a combination of experience, deliberate practice, and specific habits that accelerate the learning that experience would otherwise provide slowly.

As data-driven product management has become the norm, product sense has sometimes been devalued — positioned as the old way of doing things that analytics and A/B tests have superseded. In practice, product sense and data literacy are complementary, not competing. Data reveals patterns in past behavior; product sense is required to generate the hypotheses that become A/B tests and to interpret what patterns mean for the future.

Tip 1: Use Products Obsessively and Analytically

The fastest way to develop product sense is to use products — constantly and analytically. Not just as a user experiencing a product passively, but as a student of product design: noticing what decisions were made and why, asking “what problem was this solving?” for every feature, identifying where the design creates friction and where it creates delight.

This applies to products in your own category and to products in adjacent or very different categories. The product intuitions developed from studying exceptional products in any domain transfer to product decisions in your own domain.

Tip 2: Do Your Own User Research

Product managers who conduct their own user research — not just reviewing research reports but personally talking to users and observing them using the product — develop qualitatively different product sense than those who only consume synthesized research findings.

Direct user contact builds the emotional connection to user experience that makes product sense accurate. You develop intuitions about what kinds of friction genuinely bother users, what types of improvements produce significant versus marginal value, and what assumptions about user behavior are systematically wrong.

Tip 3: Make Predictions and Track Their Accuracy

Before A/B test results come in, predict which variant will win and why. Before a feature ships, predict what the adoption rate will be and what the most common user behavior will look like. After results are known, review the predictions you made and understand where your intuitions were accurate and where they were wrong.

This prediction-tracking practice is the most direct way to calibrate product sense — to identify the systematic errors in product intuition and the domains where intuition is more or less reliable.

Tip 4: Study Product Failures as Carefully as Successes

The product lessons contained in failures are often more instructive than those in successes, because failures reveal the assumptions that don’t hold. What feature seemed obviously valuable but wasn’t adopted? What competitive advantage turned out to be less defensible than expected? What user need proved less significant than the research suggested?

Developing the habit of studying and understanding failures — including your own — builds the pattern recognition that prevents repeating the same errors.

Tip 5: Engage with the Full Range of Product Work

Product sense is domain-specific to a degree: intuition about consumer mobile products doesn’t immediately transfer to enterprise SaaS. Developing breadth — by reading about, studying, and when possible working in different product domains — builds more generalizable product intuitions than deep specialization alone.

Key Takeaways

Product sense is developed through deliberate practice — through analytical product use, personal user research, prediction-tracking, failure study, and broad domain exposure. The product managers who develop the strongest product sense are those who treat their own judgment as an asset worth explicitly cultivating rather than as a natural endowment that either exists or doesn’t.

Share this article