Rick's signature conference exercise: "Everybody who's a practicing PM, raise your hand." Hundreds of hands go up. "Now—who came out of college WANTING to be a project manager?" Every hand drops. Except three or four.

That's the Halo Effect. And it's killing your project success rates.

In Episode 3, Rick A. Morris tackles the cognitive bias that destroys PM careers before they start—the assumption that being good at one thing automatically makes you good at another.

The Core Problem: We take our best engineer and make them a PM. We take our best PM and make them a PMO leader. We take top individual contributors and assume they'll be great people leaders.

They're completely different skill sets.

The Skill Mismatch Explained:

Great Engineer:

• Deep focus, technical mastery
• Loves solving hard problems alone
• Delivers working code/product
• Individual contributor excellence

Great PM:

• Broad stakeholder coordination
• Navigates ambiguity and politics
• Manages energy and decisions
• Influence without authority

The result? New PMs try to apply engineering rigor to people problems, get frustrated when delegation doesn't work, and burn out doing everyone's job.

Rick's PM vs. PMO Leader Insight: "A project manager colors inside the lines. A PMO manager establishes the lines everyone else colors in."

One role controls a project within constraints. The other negotiates organizational ambiguity and sets standards. Totally different skills—but we promote like they're the same.

Rick's Uncomfortable HR Truth: When Rick ran a PMO, his team hit 99% of milestones (goal was 60%). He gave everyone 5s on evaluations. HR said he couldn't—someone HAD to fall below expectations.

Their reasoning: "If you won't do this, the problem is your expectations."

Rick's response: "Or it's yours. You want me to tell high-performers they're mediocre when we're exceeding every possible expectation and building leaders? I'm not doing that."

The Lesson: Rick learned from his HR partner Carrie Blaise that preparation is everything—and now AI is his coaching preparation partner.

Three Prompts to Fight the Halo Effect:

🔹 PM Skills Gap Analysis - Identifies 8-10 core competencies, assesses strengths/gaps, delivers 90-day development plan (ChatGPT asked better clarifying questions this round)

🔹 Halo Effect Audit - Diagnoses hiring bias, surfaces overlooked skills, provides interview questions that reveal actual PM competencies (not just technical prowess)

🔹 PM Competency Framework Builder - Creates promotion rubric with "developing/proficient/expert" observable behaviors for each competency

Tool Observation: ChatGPT followed Socratic prompting better this episode. Claude kept skipping ahead to answers. Reminder: experiment with multiple tools—what works best changes by task.

Your Non-Negotiable Experiment: Run Prompt 1 (PM Skills Gap Analysis) on yourself or a PM on your team. Be honest. Identify top two gaps and one concrete action for each. Notice: Were the gaps expected? Did AI surface blind spots you've been avoiding?

Episode Timestamps:

• [03] The Halo Effect explained with conference room exercise
• [05] Engineer vs PM skill mismatch
• [06] PM vs PMO leader: coloring inside vs establishing the lines
• [08] Rick's uncomfortable HR story (the 5s controversy)
• [12] AI as coaching preparation partner
• [14] Live Demo: PM Skills Gap Analysis
• [17] Live Demo: Halo Effect Audit (hiring bias diagnosis)
• [19] Live Demo: PM Competency Framework Builder
• [21] Your weekly experiment

Resources:

• All prompts: PMThatWorks.com
• Video walkthrough: YouTube - AI Driven PM

Next Episode: People Skills vs. Domain Expertise—which one actually matters for PMs? (Spoiler: It's not what you think.)

Subscribe and share if this made you rethink how you evaluate PM talent.

Remember: Being good at one thing doesn't automatically make you good at another.

#ProjectManagement #Leadership #HaloEffect #TalentDevelopment #PMO #Coaching