Product Sense Demystified

Marty Cagan argues that "product sense" is a misleading term because it suggests an innate gift, when in reality it is deep product knowledge built through sustained immersion in a specific product space. He describes how his own product sense in software tools came from years of talking with customers, analyzing data, studying competitors, and following industry trends, which let him anticipate market shifts years ahead. He cautions that expertise in one domain does not automatically transfer to another, and that product sense should accelerate discovery rather than replace testing ideas. The piece matters because it reframes a skill people often use as an excuse into something anyone can deliberately develop.

01Key takeaways

• Treat product sense as a skill you build through deliberate immersion, not a talent you either have or lack.
• Spend real time with customers and study the data, not just the roadmap, to build understanding of your space.
• Follow competitors, industry analysts, and enabling technologies to see where your market is heading.
• Be skeptical of assuming expertise in one domain applies to another; re-earn knowledge in new spaces.
• Use product sense to guide and speed up discovery, but still validate ideas through testing.
• Doing the homework is non-negotiable for product leaders and founders, and often separates senior product managers from junior ones.

02Key sections

Why the term misleads

The word "sense" implies innate talent, which leads people to either overtrust their intuition or dismiss their own potential. Cagan says he has long avoided the term for this reason.

Product sense as deep knowledge

Strong product sense results from immersion in customers, competitors, data, and industry technology. Over time this lets a person understand current behavior and predict what comes next.

Fresh perspective versus domain experience

Contrary to expectation, outsiders without domain baggage often drive innovation, since they question dogma. Experience alone does not guarantee the deep knowledge that matters.

Cagan's own example

He describes going deep into software tools by visiting hundreds of teams, testing tools, building relationships, and speaking at conferences, which enabled 5-10 year forecasts.

Limits and caveats

Deep knowledge in one space does not transfer automatically to others, and product sense is a compass for navigating risk, not a replacement for experiments.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.