Rick's hiring conversation that challenges everything:
"So Rick, are you an expert in the insurance industry?"
"Well... shouldn't you be?"
"How many people work here?"
"Great. You've got 5,000 experts in insurance. What you need is someone like me who can get the best out of those 5,000 people."
That's the difference between domain expertise and project management expertise. And most organizations don't understand it.
In Episode 4, Rick A. Morris dismantles the conventional wisdom that PMs need deep domain knowledge—and shows why facilitation expertise matters more.
The Conventional Wisdom (Wrong):
- PMs must "speak the language" of the business
- Domain expertise = credibility and better decisions
- You need industry background to lead industry projects
Why Domain Expertise Backfires:
❌ Micromanagement - Domain experts can't resist telling people how to do the work ("I could do that in 2 hours")
❌ Focus on WHAT, not HOW - Obsessed with the solution instead of team dynamics and stakeholder alignment
❌ Personal Bias - "I've seen that approach before. It doesn't work." (Translation: It didn't work when YOU tried it)
❌ Decision Bottleneck - Every choice must run through the PM because they "understand the implications"
What Great PMs Actually Do:
✅ Ask the right questions (not provide the right answers)
✅ Translate between domains (tech ↔ business ↔ customer)
✅ Facilitate expertise (create conditions for experts to thrive)
✅ Ask the "dumb" question (that surfaces hidden assumptions)
✅ Orchestrate, don't dictate (you're the conductor, not the soloist)
Rick's Core Truth: "A great PM knows how to ask the right questions—not provide the right answers."
When Domain Expertise DOES Matter:
- Highly regulated industries (healthcare, finance) where you need to know which compliance questions to ask
- Deeply technical domains (AI/ML, embedded systems) where fluency helps translation
- Solo PM contexts where you temporarily wear both hats
Three AI-Powered Prompts to Bridge Domain Gaps:
🔹 Domain Knowledge Accelerator - Get up to speed on unfamiliar domains in days. Rick's favorite output: the coffee shop analogy for viral growth infrastructure risk ("It's like getting national press but only having one espresso machine—service will collapse")
🔹 Stakeholder Expertise Mapper - Identify who knows what, who cares about what, and role-specific questions to tap their expertise
🔹 Facilitation Over Expertise Script - Lead heated technical debates without pretending to know the answer. Example: engineering team debating microservices vs. monolith architecture—Rick shows how to facilitate the decision with authority but without technical expertise
The Power Move: "Find out who's going to make the call BEFORE you go into a full debate."
Your Non-Negotiable Experiment: Use the Domain Knowledge Accelerator on an unfamiliar area of your project. Ask at least one expert question AI generates. Notice: Did asking questions instead of pretending to know earn you MORE credibility?
- [01] The hiring conversation: "You have 5,000 experts"
- [04] Why domain expertise backfires (micromanagement, bias, bottlenecks)
- [07] What great PMs actually do (facilitation over expertise)
- [09] When domain expertise does matter
- [12] Live Demo: Domain Knowledge Accelerator (the coffee shop analogy)
- [16] Live Demo: Stakeholder Expertise Mapper
- [19] Live Demo: Facilitation Script (architecture debate)
- [22] Your weekly experiment
- All prompts: PMThatWorks.com
- Video: YouTube - AI Driven PM
Next Episode: Data-Driven Metrics 2.0—What metrics actually matter in the AI era?
Subscribe if this changed how you think about your value as a PM.
Remember: Asking questions doesn't make you weak. It makes you confident enough to admit what you don't know.
#ProjectManagement #Leadership #Facilitation #DomainExpertise #StakeholderManagement