Forward-deployed / Learning zone
Product sensea standalone module
Lesson 06

Domain expertise: turning knowledge into intuition

TL;DR

PM fundamentals transfer across industries, but domain expertise — deep knowledge of the specific world your product lives in — upgrades guessing into knowing. It acts as a filter on decisions: you can tell must-haves from nice-to-haves, anticipate what will hit resistance, and move faster because you recognize patterns. Build it deliberately — immersive learning, asking "dumb" questions, hands-on experience, a network of experts. But don't get trapped by it. Experts drift into "I am the user" and stop validating. The best domain experts pair deep knowledge with an outsider's willingness to ask "why is it done this way at all?"

🎯 For the AI PM

Why it matters — AI has two domains at once: the user's industry and the AI domain itself (what models do well, where they hallucinate, what evaluation and safety require). Thin knowledge in either produces confident, wrong product bets.

What it changes in your decisions — You learn enough of the model's failure surface to know which features are safe to ship and which need a human in the loop. You learn enough of the user's world to know where a wrong answer is merely annoying versus genuinely harmful.

Ask yourself — "In this domain, what does a confidently-wrong model output actually cost the user — and do I know that cost well enough to set the quality bar?"

Risk if ignored — Shipping an AI feature that's impressive in the demo and dangerous in the real workflow, because nobody understood the domain stakes.

Why domain knowledge strengthens intuition

Domain expertise

Turning knowledge into intuition · a filter, not a substitute for validation

The trap is "I am the user." The antidote is the outsider's question, kept alive on purpose.

Ideas, requests, signals, feature asks
Domain filter — patterns · constraints · regulations · workflows
Must-haves — recognized fast
Nice-to-haves & noise — rejected fast
The trap: "I am the user" — expert blindness sets in, and the filter stops validating.
The antidote: "why is it done this way at all?" — the outsider question, fed back into the filter.

Picture a healthcare-software PM. With thin domain knowledge you build an EMR around generic UX and obvious needs (notes, scheduling). With deep expertise you know the intricacies: HIPAA compliance, that doctors have seconds to enter data between patients, common billing issues, the politics of adopting new tools. That knowledge becomes a filter: you intuit must-haves vs. nice-to-haves, foresee what will meet resistance, and prioritize what truly adds value in context.

Experts decide faster because they recognize patterns and recall lessons from similar situations. A fintech PM who knows payments cold will quickly reject a "cool" feature whose compliance approval would take a year, and find a creative path that meets the need without the red tape. A novice would charge in and hit the wall.

Domain knowledge also builds credibility: speaking your users' and stakeholders' language makes you a more persuasive communicator and a more trusted decision-maker — sales and marketing back your calls when they see you truly understand the market.

But it must complement, not replace, the rest. Marty Cagan's warning: experts get entrenched, assume they are the user, and overlook new perspectives. Domain expertise is a turbocharger for product sense — used wisely, it lets you skip the basics and focus on the subtleties outsiders miss — but only if you keep validating.

Building it (without getting trapped)

Entering a new domain, be systematic:

Balance with fresh perspective. A newcomer's "why is it done this way at all?" sometimes becomes a breakthrough, precisely because they don't accept "that's just how it is." As you gain expertise, preserve that outsider curiosity: rotate people across domains, keep validating with real users, and don't let expertise curdle into arrogance — "constantly revisit assumptions about the domain and customers," because new regulations, behaviours, and competitors will surprise you.

Tackling AMAs — expertise on display

An AMA (Ask Me Anything) is a stress test for domain mastery. Imagine leading a crypto product when a customer asks, "with the new crypto tax rules, how does this wallet help me report transactions?" Deep expertise lets you explain the rule change and point to the specific (or planned) tax-reporting features — even citing conversations with tax experts. A teammate's forward-looking "will DeFi threaten our approach?" draws on your strategic view of how you differ and coexist.

Preparing for an AMA is itself a learning exercise — it forces you to anticipate what knowledgeable people will ask, refreshing your understanding. Comfortably fielding tough Q&A signals to executives that you're on top of the domain and to your team that they can trust your guidance. And when you can't answer, knowing where to find it — or having an informed hypothesis — is itself the mark of expertise.

Actionable steps

📦 Mini-case — the EMR that doctors hate. Electronic medical records were largely designed with deep domain input — from billing and compliance experts. The result optimizes claims perfectly and forces clinicians through fifteen clicks to record an ordinary visit. Domain expertise was present. It was the wrong domain's, and nobody asked the outsider question "why does a doctor's tool feel like an invoice?" Expertise tells you how the world works. Only user contact tells you whose version of the world your product just encoded.

Failure modes

Practitioner checklist