They say yes to too many projects. They commit to impossible dates. They overload their best people. And then six months later, they wonder why nothing finished on time and everyone's burned out.

By the time a project is in trouble, the decision that caused it was made months earlier — in a hallway conversation where someone was too uncomfortable to tell the truth and someone else was too optimistic to hear it.

In the Season 2 finale of AI Driven PM, Rick A. Morris introduces Gatekeeper — a portfolio intake intelligence agent that sits at the front of the portfolio before a project gets approved, before a date gets committed, before a team gets assigned. She asks the hard questions humans avoid. And she doesn't soften the answers.

Four Gates. No Exceptions:

🔹 Gate 1: Scope Clarity — Is the scope defined well enough to estimate? Vague requests go to "discovery required." This gate alone would stop half the bad projects approved every year.

🔹 Gate 2: Realistic Estimation — Atlas practice libraries + PERT methodology = a range, not a single number. If the requested date falls outside the range, Gatekeeper flags it at intake — not six months later.

🔹 Gate 3: Capacity Analysis — Current portfolio load, team utilization, in-flight projects. "Current portfolio is at 112% capacity. Adding this project increases that to 127%." No more "we'll figure it out."

🔹 Gate 4: Risk and ROI Alignment — ARIA-style risk assessment vs. expected business value. High-effort, high-risk, low-value projects get flagged. Political pet projects get the same scrutiny as everything else.

Live Demo — Phoenix Platform Modernization: All-or-nothing bundle. 50% failure probability. 930Katrisk.Only600K in opportunity cost displaced. Break-even requires $5.55M/year in savings. Gatekeeper recommended a phased approach. Math on the table before the bet is made.

The Deep Diagnostic: Rick answered what they were building but not why. Gatekeeper stopped him: "You answered what. You didn't answer why." Three-month timeline for monolith-to-microservices (industry standard: 9-18 months) flagged immediately. Failure probability: 50-70%. Recommendation: 150Ksingle−servicepilottoavoida1.25M failure. Produced a branded one-page decision record for executives.

The Hard Truth: Most organizations don't have a capacity problem — they have a discipline problem. They know the dates are unrealistic. They approve them anyway. Gatekeeper puts the data on the table before the decision. Leadership can't blame delivery teams for missing dates they chose with full information.

The Season 2 Arc — Full Circle:

• Episodes 1-9: Socratic prompting and AI as thinking partner
• Episode 10: ARIA — risk intelligence from organizational history (the lessons learned system Rick described in 2008, finally possible)
• Episode 11: Atlas — estimation discipline, now automated
• Episode 12: PACE — execution accountability, now measurable
• Episode 13: Gatekeeper — portfolio governance, now enforceable

These agents amplify human judgment. They don't replace it. ARIA doesn't decide which risks to mitigate — you do. Atlas doesn't approve the estimate — you do. PACE doesn't reduce sprint capacity — you do. Gatekeeper doesn't decide which projects to approve — leadership does. She just forces the conversation.

The technology has finally caught up to the vision.

Rick's Final Challenge: Stop playing games with impossible dates. Stop pretending you have capacity you don't have. Stop repeating the same mistakes because nobody captured the lessons. Use AI to tell the truth. Use AI to force the hard conversations. Use AI to protect your teams.

Because we are not here to fill out forms and update trackers. We are here to make dreams come true.

Thank you for Season 2. Now go build something great.

#ProjectManagement #AI #PortfolioManagement #PMO #Gatekeeper #AIDrivenPM #Leadership #Agile #ProjectSuccess #MakeDreamsComeTrue

Most agile teams can't answer that. Not because the data doesn't exist — it does, sitting in Jira, Azure DevOps, or a spreadsheet right now. Because nobody has built the engine to surface it.

In Episode 12, Rick introduces PACE — the Predictability and Capacity Engine — the third AI agent in his production system series. PACE tells you the truth about your agile teams: not just what they delivered, but whether they're getting more or less disciplined over time, and exactly why.

The Metric Problem: Velocity, burn down, and story points are lagging indicators. They show what happened. They don't tell you why stories slipped, whether you're improving or degrading, or what to do about it. Velocity going up might just mean you're getting faster at rolling unfinished work to the next sprint.

The Distinction That Changes Everything: Is the problem capacity (team size, sprint commitment) or readiness (stories entering sprint without clear requirements, designs, or resolved dependencies)? You cannot fix a readiness problem by adding people. PACE separates them — every sprint, every team, over time.

Two Metrics That Actually Matter:

📊 Slide Rate — % of committed stories that don't finish in their sprint. Target: under 10%. Warning: above 20%.

📊 Readiness Debt — % of stories entering sprint unready. This is a leading indicator. 40% readiness debt will cause slide. Not if. How much.

The Real Client Story: Large financial services company. 43 sprints. 48,621 Jira issues analyzed. Surface metrics looked healthy — velocity up, cost per story point down. PACE found the team wasn't getting worse at execution. They were getting worse at readiness — and it was accelerating. Slide rate climbed from 11.8% to 18% to 28% for the new team. The instinct was to ask "how do we increase velocity?" PACE revealed the real question: "Why are we accepting unready work?"

Four PACE Deliverables:

• Color-coded sprint dashboard (green/yellow/red by slide rate and readiness thresholds)
• Best and worst sprint identification (best = proof the team CAN be predictable; worst = investigation targets)
• Trend narrative ("slide rate increased from 10% to 25% — this is a process problem, not a people problem")
• Targeted action recommendations based on what the data actually shows

Rick's Signature Metric: Cost Per Story Point Not just "did velocity increase?" but "did we get more done per dollar?" When you add 40 people, PACE shows whether you actually got more efficient — and what additional work was accomplished. Metrics that were previously impossible to calculate.

The Discipline Paradox: Discipline feels like friction. Readiness checks, pushing back on unready stories — it feels like slowing down. But discipline is what makes teams fast. When stories enter ready, they complete on time. When sprints finish clean, velocity stabilizes. When commitments hold up, stakeholders trust you. PACE measures that discipline.

Portfolio Scale: Run PACE across 10, 20, or 100 teams. Compare Team A (8% slide) to Team B (30% slide) on similar work. Spread what works. Organizational learning at portfolio scale — from data that already exists in your sprint tools.

PACE + ARIA: ARIA (Episode 10) = project-level health. PACE = team execution discipline. Together they answer: "Is this project healthy?" and "Is this team predictable?" PACE's forward-looking health check flags current sprint issues before the sprint closes — no more waiting until it's too late.

Next Episode: Gatekeeper — the portfolio intelligence agent that decides which projects should even start. Most organizations say yes to too many things. When everything is a priority, nothing is. Gatekeeper forces the hard conversations before commitment, not after.

Remember: Discipline isn't friction. It's what makes you fast.

Bad estimates don't happen because PMs are bad at math. They happen because we're asked to make precision commitments at the exact moment we know the least. And then we spend the rest of the project defending a number we never should have been asked to give.

In Episode 11, Rick introduces Atlas — the AI estimation agent built and deployed in production to solve the estimation problem at its root.

What Atlas does:

• Maintains a versioned practice library — every service type your org delivers, with roles, rates, phases, modules, and three-scenario effort estimates per component
• Guides PMs through a structured estimation conversation, module by module, grounded in your delivery history
• Produces three-scenario PERT estimates (optimistic, most likely, pessimistic) with fully formula-driven Excel workbooks — not a single number, a defensible range

Two modes. One engine. Standard workflow: you know the project shape, Atlas builds from the practice library. Discovery mode: you hand Atlas an RFP or requirements document and she analyzes it, suggests component counts, and asks you to validate before a single hour is estimated.

The 500-requirements demo: Real Salesforce implementation. Atlas ran 500 requirements through discovery mode, returned component counts (4 data objects, 11 workflows, 20 scripts, 13 reports, 23 custom fields), generated a structured assumptions document for architect review, and produced a third-revision estimate — in about one hour total. PERT output: 1.1Mto5.7M range, $1.8M expected value. What used to take days of line-by-line senior-architect review.

Why three scenarios beat one number: A single estimate creates false precision. Three scenarios communicate uncertainty honestly, give clients room to understand what drives the number, and set up scope conversations that are evidence-based — not subjective. "We estimated 11 workflows, there are 17" is a defensible conversation.

The RFP scenario: Client needed componentized pricing in their specific format by Friday. Atlas took the RFP, the existing estimate, and the client's format — and produced a structured response with assumptions, PERT parameters, and best/most likely/worst case. Wednesday to Friday. Done.

The Atlas-ARIA closed loop: Atlas builds the estimate at the start. ARIA protects it during execution. When the project closes, actuals update the practice library AND feed ARIA's risk database. Both systems get smarter. Organizational learning encoded into systems that don't forget.

The transformation: Estimation from 4 hours to 10 minutes. From PM-to-PM variance to organizational consistency. From hedging to authority. From "I think it's around this" to "here's what it costs, here's why, here's the math."

Next episode: PACE — the Predictability and Capacity Engine. Portfolio-level agile predictability, sprint commitment discipline, and readiness debt.

#ProjectManagement #AI #Estimation #PERT #PMO #ArtificialIntelligence #PMP #Agile #PortfolioManagement #AIDrivenPM #Atlas #ScopeControl

Episode 10 marks a major series pivot. Rick A. Morris introduces ARIA—the Advanced Risk Intelligence Agent—a production system running on real client projects right now. Not a proof of concept. Not a demo. Live.

The 2008 Vision: In 2008, Rick wrote two books describing the future of PM: organizational memory systems that captured lessons learned from every project and automatically applied them to new ones. Mathematical risk profiles based on actual history. A database that weighted patterns by severity and repeatability.

What killed it: The manual effort. When the person maintaining the system left, the knowledge left with them.

What changed in 2024: Large language models finally caught up to the idea.

The Problem with Current Risk Management:

• Risk register templates unchanged for 20 years
• Probability/impact scores based on gut feel
• Lessons learned filed away and forgotten
• "We've been doing this for decades. It's absolutely insane."

Why ARIA Is Different from ChatGPT: ChatGPT gives you generic PMBOK-based risk lists. ARIA knows YOUR organization's history:

• That your vendor management breaks down on projects over $2M
• That your design phase runs 30% long with remote teams
• That your change control only works with a specific executive sponsor

The Math: PERT Methodology Developed by the US Navy for the Polaris missile program. Three scenarios: Optimistic, Most Likely, Pessimistic (pulled from your historical database). Expected Value = (O + 4M + P) ÷ 6. Statistically sound. Not a guess.

ARIA's Six Modes:

1. Lessons Learned Ingestion - Fuel for everything
2. Risk Assessment - Full Excel workbook in minutes
3. Risk Coach - Targeted guidance in the moment
4. Project Closeout - Structured interview, closed loop
5. Project Health Check - 8-dimension color-coded assessment
6. Maintenance - Database quality management

Live Demo Results: Dynamics 365 implementation, 2.1M(cut222.7M), fixed price, thin requirements, like-for-like ERP replication.

ARIA's immediate flag: "These characteristics align almost exactly with the single highest-severity record in the entire database."

10 minutes later: Excel workbook with 129 business days contingency, $1.43M (68% of contract), confidence band of 91-167 days, full PERT calculations, complete risk register with mitigation strategies, and an executive narrative—presentation ready.

The Credibility Difference: "I think we need a buffer" vs. "This project shares characteristics with 12 historical engagements. Those engagements slipped an average of 68 business days. Here's the data."

The Closing Truth: ARIA is your organization's memory. She doesn't forget. She doesn't retire. Every project that closes makes every future risk assessment smarter. This is the closed loop PMBOK has always described but we've never had the tools to execute—until now.

Episode Timestamps:

• [00] Series pivot: from theory to production systems
• [02] The 2008 vision and why it failed
• [05] The problem with current risk management
• [08] Why ARIA is different from generic AI
• [09] PERT methodology explained
• [11] ARIA's six modes walkthrough
• [14] Live risk assessment demo: Dynamics 365 manufacturing implementation
• [20] Excel output walkthrough: executive summary, PERT calculations, risk register
• [22] What this means for PM credibility and the profession

Resources: PMThatWorks.com | YouTube - AI Driven PM

Next Episode: Atlas—the estimation engine. Front-end estimates built with the same rigor as ARIA's risk management. Practice libraries, PERT modeling, production-ready workbooks.

Subscribe if you're ready to see what AI-powered PM actually looks like in production.

Remember: AI shouldn't replace project managers. It should amplify us.

#ProjectManagement #AI #RiskManagement #PERT #PMO #AgentBuilding #ArtificialIntelligence #ARIA

"If you give somebody the answer, you rob them of a lifetime of learning."

In Episode 9, Rick A. Morris makes the case that in the AI era, coaching is no longer optional for project managers—it's the entire job.

The Problem with Directive Leadership: Rick used to be a directive leader. He had the answers. He gave them freely. And every time he tried to take a vacation, his phone wouldn't stop ringing. His team couldn't function without him—not because they weren't capable, but because he'd never let them discover their own capability.

The AI Era Shift: AI can automate task management, scheduling, reporting, and requirements. What it cannot touch: conflict navigation, emotional safety, capability building, and helping humans work through ambiguity and fear.

"Teams don't need bosses anymore. They need coaches who help them perform at their best."

Manager vs. Coach:

• Manager provides answers → Coach asks questions
• Manager directs action → Coach creates space for discovery
• Manager extracts work → Coach builds capability
• Manager creates dependency → Coach builds ownership

The Brendan Bouchard Moment: Rick shares his most powerful coaching story. He was venting to Brendan about a difficult team member when Brendan asked one question that stopped everything:

"What did he say when you told him all this?"

Rick hadn't told him. Not a word.

One question. A lifetime of learning. That's coaching.

Three AI-Powered Prompts Demonstrated Live:

🔹 Coaching Conversation Planner - Prepare for a real coaching conversation with a withdrawing team member. Claude's standout opening: "Sarah, I wanted to carve out some time that isn't about tickets or sprint status. How are you actually doing?" Full stop. Let her decide how much to give you.

🔹 Powerful Coaching Questions Library - Build a reusable question bank organized by situation: stuck team member, conflict, underperformer, career growth, resistance. Plus the critical principle: Don't lead the witness. ("Don't you think we should...?" vs. "What options do you see?")

🔹 Conflict Coaching Facilitator - Navigate the architecture debate between Sarah and Tom. Claude's insight: "Architecture debates between senior engineers rarely stay technical this long unless something else is driving them. This conflict has three layers—risk tolerance, identity/credibility, and decision authority ambiguity. Until you address layer three, the others keep feeding each other."

Core Coaching Skills for PMs: ✅ Active listening (what's NOT being said) ✅ Powerful questions (help people think differently) ✅ Holding space (pause, create safety) ✅ Capability building (develop people, don't just extract work) ✅ Accountability with empathy (high standards + high support)

Your Non-Negotiable Experiment: Use the Coaching Conversation Planner to prepare for a real conversation this week. Ask at least three coaching questions—and resist the urge to answer them yourself. Notice: Do people arrive at solutions you hadn't thought of?

Episode Timestamps:

• [01] Christian Simpson and the quote that changed everything
• [03] The directive leader problem (why Rick's vacations were disasters)
• [04] The AI era shift: tasks automated, human side remains
• [06] Manager vs. coach mindset
• [07] Core coaching skills for PMs
• [09] Live Demo: Coaching Conversation Planner (the Sarah situation)
• [17] The Brendon Burchard story (best coaching moment of Rick's career)
• [19] Live Demo: Powerful Coaching Questions Library
• [23] Live Demo: Conflict Coaching Facilitator (Sarah vs. Tom)
• [27] Your weekly experiment

Resources: PMThatWorks.com | YouTube - AI Driven PM

Next Episode: Work-Life Balance 2.0—how AI changes the always-on PM trap.

Subscribe if this made you rethink how you lead your team.

Remember: The tasks are getting automated. The human side of projects is becoming your entire job.

In Episode 8, Rick A. Morris shares a lesson from his personal development journey—the Three R's taught by coach Paul Martinelli—and connects it directly to why your change initiatives are failing.

The Three R's:

🔴 Resistance - Passive non-compliance. "I'll wait until this blows over."

🔴 Revenge - Active demonstration that the change doesn't work. Double-tracking. Slack complaints. Visible friction.

🔴 Resentment - Emotional withdrawal. "Leadership doesn't care. Nobody reads these reports anyway." Once here, the relationship is over.

The Core Truth: "People don't resist change. They resist being changed."

69% of the population is High S (DISC). They love routine. They will change—but not because you announced it, ran a 90-minute training, and disappeared.

Why Change Initiatives Really Fail:

• Change is done TO people, not WITH them
• Focus on the WHAT (tool, process) while ignoring the WHO
• No clarity on why the change matters
• No voice or input in how the change happens
• Broken trust from past failed initiatives
• Leaders disappear after the kickoff
• Training, change management, and PM are cut from budgets

The AI Change Warning: AI rollouts are more personal than any previous technology adoption. People feel automated out of relevance. Without managing the people side, even great AI tools will fail.

Rick's Clarity Tool Story: After years of project rescue work, Rick found that resentment toward a failed tool was nearly impossible to overcome—even when rebuilding from scratch. He had to transition his business from rescue to implementation because the resentment gap was too wide to cross.

Three AI-Powered Prompts Demonstrated Live:

🔹 Change Readiness Diagnostic - Diagnose where your team sits on the change spectrum and get a 30-day action plan. Claude's standout insight: "This is not a training problem or a tool problem. It is a trust problem with a workflow mismatch layered on top."

🔹 Resistance Root Cause Analyzer - Identify whether you're seeing passive, active, avoidance, or sabotage resistance—and surface the underlying fears driving it (incompetence, job security, workload, broken trust)

🔹 Co-Creation and Ownership Strategy - Design a strategy where people shape HOW the change happens, not just accept WHAT was decided. Claude's key reframe: "When they build it, it stops being yours."

The Metric Rick Loved: Number of times leadership references the new tool's data in informal settings. Not a usage metric—a trust metric.

Your Non-Negotiable Experiment: Run the Change Readiness Diagnostic on a current or recent change initiative. Take one action: invite co-creation or directly address a root cause of resistance. Notice: Does giving people a voice shift sentiment—even when the change itself is non-negotiable?

Episode Timestamps:

• [01] Paul Martinelli and the Three R's (personal development origin)
• [03] The Three R's in change management (resistance, revenge, resentment)
• [04] People don't resist change—they resist being changed (the 69% insight)
• [06] Why change initiatives fail (and why we always cut the wrong things)
• [08] AI change management is uniquely personal
• [10] The Clarity tool rescue story
• [13] Live Demo: Change Readiness Diagnostic
• [20] Live Demo: Resistance Root Cause Analyzer
• [23] Live Demo: Co-Creation and Ownership Strategy
• [27] Your weekly experiment

Resources: PMThatWorks.com | YouTube - AI Driven PM

Next Episode: Coaching First, PM Second—why facilitation is your most valuable skill in the AI era.

Subscribe if this changed how you think about change management.

Remember: Catch it at resistance. That's where change is still recoverable.

That's the greatest lie ever told in project management.

You don't own the people. You don't control the budget. You didn't set the strategy. You don't decide the timeline. But when things go wrong? Everyone looks at you.

In Episode 7, Rick A. Morris makes the case that influence is the single most important skill a PM can develop—and shows you how to use AI to map, craft, and execute influence strategies that actually work.

The Reality of PM Authority:

• People don't report to you
• It's not your money
• It wasn't your idea
• You don't own the outcome

What you do own: the percentage chance of success. By doing analysis, framing decisions, and influencing whoever you're speaking with toward the right outcome.

The Three Currencies of Influence:

💰 Credibility - People trust your judgment because you've earned it (not because of your title)

💰 Reciprocity - You help others achieve their goals, and they help you achieve yours (the most powerful lever PMs have)

💰 Vision - You paint a picture of success so compelling that people want to contribute

Common Influence Mistakes PMs Make: ❌ Over-relying on logic ("surely they'll see the math") ❌ Positional pleading ("the CEO said so") ❌ Passive aggressive escalation ("I guess I'll have to escalate...")

The DISC Secret Weapon: One message. Four different ways to say it. High D wants bullet points. High C wants data. High S needs to understand change impact. High I wants to know what's exciting. Meeting people where they are isn't manipulation—it's respect.

Three AI-Powered Prompts Demonstrated Live:

🔹 Influence Network Mapper - Maps key influencers, identifies positions/motivations, recommends tactics, and builds a sequencing strategy. Claude's standout insight: "You're not building consensus. You're building a sequence of aligned conversations so that by the time you reach the CEO, the decision feels inevitable rather than contentious."

🔹 Stakeholder Persuasion Message Crafter - Craft messages that land. The Netflix analogy AI generated: "Netflix didn't launch with a recommendation engine. They launched with the catalog. An AI feature trained on zero user behavior doesn't differentiate you—it could embarrass you."

🔹 Reciprocity & Coalition Builder - Build genuine influence through service, not transactions. Rick's honest tool critique: Claude's suggestion to explicitly name a past favor was too direct. ChatGPT's approach—aligning the ask with their interests and removing burden—was more effective. (Yes, Rick will tell you when AI gets it wrong.)

The Sequencing Strategy: Engineering manager → Product owner → Marketing director → CEO. Pre-wire every conversation so the final meeting is a confirmation, not a confrontation.

Your Non-Negotiable Experiment: Use the Influence Network Mapper on a real decision you need to influence this week. Have at least one conversation using the strategy AI helps you design. Notice: Did mapping reveal leverage points you hadn't considered?

Episode Timestamps:

• [01] The greatest lie in PM and the authority gap
• [04] Three currencies of influence (credibility, reciprocity, vision)
• [06] Common influence mistakes that kill credibility
• [07] DISC as an influence tool
• [09] Live Demo: Influence Network Mapper + sequencing strategy
• [17] Live Demo: Stakeholder Persuasion Message Crafter (Netflix analogy)
• [21] Live Demo: Reciprocity & Coalition Builder (+ Rick's honest AI critique)
• [27] Your weekly experiment

Resources: PMThatWorks.com | YouTube - AI Driven PM

Next Episode: The Three R's—Resistance, Revenge, and Resentment. Why change initiatives fail and how to navigate your way out.

Subscribe if this changed how you think about your role as a PM.

Remember: The most effective PMs don't win by being the loudest. They win by knowing exactly who to talk to, in what order, with what message.

Here's why: They weren't evaluating your project. They were evaluating your portfolio.

In Episode 6, Rick A. Morris introduces Net Operating Value (NOV)—the metric that closes the gap between how PMs talk about projects and how executives actually make decisions.

The Core Problem: PMs optimize in isolation. Executives optimize across competing priorities. Without a shared language for value, they talk past each other—and great projects get killed while mediocre ones survive.

Net Operating Value Formula: NOV = Expected Value − Effort Cost − Risk Cost − Opportunity Cost

That last variable is what most business cases never include. And it changes everything.

"ROI asks: Is this worth doing? NOV asks: Is this the BEST thing we could be doing with these resources right now?"

The AI Capacity Trap: Teams see velocity increase with AI and assume: more capacity = more projects. Wrong question. The right question isn't "Can we build it?" It's "Should we build it—given everything else we could build?"

Three AI-Powered Prompts Demonstrated Live:

🔹 NOV Calculator - Calculate full project NOV including opportunity cost. Live result for Social Wishing: **Negative 280K return. AI verdict: "This is not an investment. It's an experiment with negative expected value."

🔹 Value Assumption Stress Test - Identify which assumptions, if wrong, kill the entire value case—then find the cheapest way to validate them. Claude's diagnosis: "This is not a 25,000 behavior experiment." Rick's favorite reframe: "Can we spend $15,000 over 45 days to find out if we should build this before committing the remaining budget?"

🔹 Portfolio Trade-Off Analyzer - Compare competing projects on NOV, identify must-dos vs. nice-to-haves, and communicate trade-offs without killing morale. Result: Greenlight the "cash generator" + "capability builder." Kill Social Wishing (for now). "Don't frame it as killing creativity. Frame it as disciplined capital allocation."

The Full Circle Moment: The Social Wishing app—built all season—fails the NOV test. That's not failure. That's exactly how great project management works. Dreams deserve data before dollars.

Your Non-Negotiable Experiment: Run the NOV Calculator on a current project. Then identify the one assumption that, if wrong, kills the entire value case—and test it.

Notice: Does including opportunity cost change how executives respond to your business case?

Episode Timestamps:

• [01] Why executives kill winning projects
• [03] NOV defined: Expected Value − Effort − Risk − Opportunity Cost
• [04] The AI capacity trap ("Can we?" vs. "Should we?")
• [07] Live Demo: NOV Calculator (Social Wishing gets brutalized)
• [15] Live Demo: Value Assumption Stress Test
• [22] Live Demo: Portfolio Trade-Off Analyzer
• [27] Your weekly experiment

Resources: PMThatWorks.com | YouTube - AI Driven PM

Next Episode: Influence Without Authority—how to lead when you can't command. Not your idea. Not your people. Not your budget. How do you move the needle anyway?

Subscribe if this changed how you think about project value.

Remember: Protecting your project means proving it deserves the resources over everything else competing for them.

#ProjectManagement #PortfolioManagement #NOV #BusinessCase #AI #Leadership #PMO

In Episode 5, Rick A. Morris—a Six Sigma practitioner and data obsessive—exposes the metrics trap most PMs fall into and shows you how to build dashboards that actually answer the questions that matter.

The Core Problem: Activity metrics measure busyness. Outcome metrics measure results. Most PMs are tracking the wrong ones.

The Lawyer Analogy: PMs build cases. Sponsors are judges. If you have more data than the person you're presenting to, you win the conversation. But only if the data tells the right story.

"It's not a data problem. It's a framing problem. You're reporting inputs when executives are asking about outcomes." — Claude's blunt assessment

What You Should Actually Be Measuring:

✅ Value Delivered - Features in production being used (not just shipped)

✅ Time to Impact - How fast from idea to user value?

✅ Quality Signals - Defect rates, technical debt, user satisfaction

✅ Team Health - Velocity stability, morale, sentiment (not just velocity)

✅ Stakeholder Confidence - Sponsor engagement, meeting attendance

Rick's Signature Metric: Scope Stability Index New story points added ÷ total committed story points. If it exceeds 15% mid-sprint, execution predictability collapses. This is how you show sponsors the real cost of mid-sprint scope changes—with data, not arguments.

The GrowthDay Lesson: A last-minute feature became the app's stickiest element. Rick only knew because he measured how users actually engaged with it. If you're not measuring features being used—not just shipped—you don't know if you're delivering value.

Three AI-Powered Prompts:

🔹 Metrics Dashboard Designer - Build a dashboard that answers executive questions with outcome metrics, leading indicators, green/yellow/red thresholds, and audience-specific presentations

🔹 Predictive Risk Indicator Finder - Surface leading indicators of trouble before it arrives. Rick's standout AI insight: code review comment density per PR reveals whether slow reviews mean complexity or avoidance—and they require different interventions

🔹 Vanity vs. Value Metrics Audit - Diagnose your current report and swap vanity metrics for value metrics. Six out of eight common PM metrics are vanity. Find out which ones—and what to replace them with.

AI's Role in All of This: AI can automate all the activity tracking—leaving you free to focus on outcome measurement, impact analysis, and inventing metrics that tell the parts of the story nobody else is telling.

"AI can't do for you what it can't do through you."

Your Non-Negotiable Experiment:

1. Build your outcome metrics dashboard using Prompt 1
2. Replace at least one vanity metric in your next status report with a value metric Notice: How do stakeholders react when your report actually answers their questions?

Episode Timestamps:

• [02] Data rules everything—but we're measuring wrong
• [04] Activity vs. outcome metrics explained
• [06] The lawyer analogy: building cases, not reports
• [08] What to actually measure (value, time to impact, quality, team health)
• [11] AI's role in automating tracking vs. freeing PMs for outcomes
• [13] Live Demo: Metrics Dashboard Designer
• [19] Live Demo: Predictive Risk Indicator Finder
• [24] Live Demo: Vanity vs. Value Metrics Audit
• [28] Your weekly experiment

Resources: PMThatWorks.com | YouTube - AI Driven PM

Next Episode: Net Operating Value—how to stack-rank your portfolio and make trade-off decisions using data that reflects real business value.

Subscribe if this changed how you think about data and project reporting.

Remember: The PM who tells the better story wins.

#ProjectManagement #Metrics #DataDrivenPM #AI #Agile #PMO #Leadership

"So Rick, are you an expert in the insurance industry?"

"No."

"Well... shouldn't you be?"

"How many people work here?"

"About 5,000."

"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?

Episode Timestamps:

• [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

Resources:

• 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

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

Answer: Everything that actually matters.

In Episode 2, Rick A. Morris tackles the 60/40 problem—why most PMs spend 60% of their time on busy work and only 40% creating real value—and shows you how to flip that ratio using AI as your thinking partner.

The Core Truth: AI handles the transactional. PMs handle the transformational.

The Four Things PMs Do That AI Can't Replace:

✅ Sense Making - Translating chaos into clarity for stakeholders (AI can summarize, but can't make sense of the why)

✅ Decision Architecture - Designing how decisions get made and by whom (you don't make decisions—you design the process)

✅ Energy Management - Regulating team motivation and creating conditions for innovation (AI can't facilitate the conversation that rebuilds trust)

✅ Conflict Resolution - Navigating competing priorities and personalities (AI can't build relationships or read the room)

Three Power Prompts Demonstrated Live:

🔹 Project Health Diagnostic - Surface the top 3 risks, identify stakeholder gaps, find the decision being avoided, and get the one action with highest impact this week

🔹 Decision Architecture Mapper - Design governance for strategic, tactical, technical, resource, and scope decisions with clear RACI

🔹 Energy Audit - Identify where team energy is highest/lowest, spot misalignment, and craft the narrative to re-energize your team

Live Demo Insight: Rick runs all three prompts in ChatGPT and Claude side-by-side using the Social Wishing app project. Claude delivers exceptional coaching—not just diagnostics, but how to have the hard conversations with empathy and strategic framing.

Standout Claude coaching example: "The sponsor isn't being malicious. They genuinely don't see the downstream impact of small additions. The goal isn't to win an argument—it's to get them into the same decision-making frame as the team."

Your Non-Negotiable Experiment: Run the Project Health Diagnostic on one real project this week using meeting transcripts, emails, or status reports. Act on at least one insight. Notice: Did AI surface something you were avoiding? How much time did you save?

Episode Timestamps:

• [02] The 60/40 problem explained
• [05] Four things PMs actually do (sense making, decision architecture, energy management, conflict resolution)
• [09] AI = transactional, PM = transformational
• [12] Live Demo: Project Health Diagnostic (ChatGPT vs Claude)
• [20] Live Demo: Decision Architecture Mapper
• [24] Live Demo: Energy Audit
• [28] Your weekly experiment

Resources:

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

Next Episode: The Halo Effect—why we keep promoting the wrong people into project management and how to become the transformational leader your team needs.

Subscribe and share if this changed how you think about your role as a PM.

Remember: You're not a project secretary. You're a dream translator.

#ProjectManagement #AI #Leadership #TeamDynamics #ProjectGovernance #ChatGPT #Claude

🎯 Here's the uncomfortable truth: AI won't replace project managers. But you will absolutely be replaced by a project manager who knows how to leverage AI.

In this season premiere, Rick A. Morris introduces Socratic prompting—a technique that turns fuzzy sponsor dreams into clear vision, team motivation, and a first backlog in under 10 minutes.

What You'll Learn:

✅ The PM Identity Reframe - Why you're a dream translator, not just a scheduler

✅ The Value Paradox - Where PMs actually add value (it's not status reports)

✅ Socratic Prompting - How to treat AI as a thinking partner, not a typing service

✅ Three Game-Changing Prompts:

• Vision Clarifier: Fuzzy idea → Clear, measurable vision
• Charter to Dream Story: Vision → Team motivation + mantra
• Dream to Backlog: Vision → Prioritized features with rationale

✅ Live Demo - Rick takes a vague app idea ("Social Wishing") and generates vision, measurable outcomes, team motivation, 5 mantras, and 15 prioritized backlog items in 10 minutes using ChatGPT and Claude side-by-side.

Key Insight: Most PMs spend 80% of their time looking backwards (status updates, documentation). AI shifts that ratio—letting you spend 80% looking forwards (anticipating needs, clearing blockers, mitigating risks). That's where real value lives.

Your Non-Negotiable Experiment: Use the Vision Clarifier prompt on one real, fuzzy sponsor idea this week. Notice how asking clarifying questions first changes the conversation—you get to the "why" faster instead of arguing about the "what."

Episode Timestamps:

• [02] The dream translator identity
• [05] Why AI won't replace PMs (but PMs using AI will)
• [08] The value paradox explained
• [10] What is Socratic prompting?
• [13] Live Demo: Vision Clarifier
• [18] Live Demo: Charter to Dream Story
• [23] Live Demo: Dream to First Backlog
• [27] Your weekly experiment

Resources:

• All prompts: PMThatWorks.com
• Video walkthrough: YouTube - AI Driven PM
• Connect: Links in show notes

About Rick A. Morris: 30+ years, 150+ PMO implementations, 7 books, host of "Work-Life Balance with Rick A. Morris." Rick helps organizations stop playing games and start delivering results.

Next Episode: What do PMs really do in an AI world once busy work is gone?

Subscribe and leave a review if this changed how you think about AI and project management.

Remember: You're not here to fill out forms. You're here to make dreams come true.

#ProjectManagement #AI #ChatGPT #Claude #ProductManagement #Leadership #PMO

Rick outlines specific ways agents can enhance project management: from real-time analysis of project timelines and resourcing, predictive modeling to preempt project bottlenecks, to sentiment analysis on project communications to monitor stakeholder satisfaction. He gives a compelling example of agents autonomously assessing project health by examining risk logs, tracking updates, and providing project managers with targeted insights and actionable recommendations.

He also explores how agents can simplify the often arduous administrative tasks in Agile workflows, envisioning agents that handle everything from cost analysis to sprint reports, allowing project managers to focus on strategic insights. For Rick, AI agents offer an opportunity to automate repetitive tasks, reduce human error, and allow PMs to focus on forward-looking analytics and high-impact decision-making.

Rick closes the season by inviting listeners to provide feedback and insights for season two, with a promise to explore these AI tools further as they come online. Looking ahead, he anticipates collaborating with leading experts, diving deeper into practical AI applications, and creating a hands-on, interactive learning experience for project managers ready to integrate AI into their practices.

Joe Ours Webinar: https://centricconsulting.com/ub_nat_ai_agents_wbnr/

The episode emphasizes that while many organizations invest in portfolio management tools to address project management issues, they often underestimate the quality of data required. Rick discusses common issues, such as the challenges in defining project scoring and ranking criteria, especially in balancing metrics like ROI, risk, and strategic alignment. He argues that AI can alleviate this by analyzing vast datasets to develop optimized, data-driven criteria and innovative project insights.

Rick highlights specific AI capabilities, such as leveraging historical project data for predictive analytics, which allows for accurate forecasting of ROI and risk. He also introduces the concept of dynamic, ongoing portfolio balancing through simulation models and scenario analysis, made possible by AI’s processing power. Ultimately, he sees AI as a game-changer that enables PMs to refocus on strategic oversight rather than manual data handling.

Rick wraps up by reinforcing that AI won’t replace project managers but will elevate those who know how to harness it effectively. This episode is a compelling vision of how AI can redefine the role of PMOs in strategic alignment and operational efficiency, preparing project managers for a future where AI-driven insights become integral to decision-making.

He introduces innovative strategies to improve the facilitation of these meetings by leveraging AI tools like ChatGPT. Rick outlines practical steps for collecting anonymous feedback, analyzing it using sentiment analysis, and facilitating discussions that focus on key issues like team dynamics, workload, and stress. He also demonstrates how AI can help craft actionable insights from the feedback, ensuring that retrospectives lead to meaningful improvements.

The episode is packed with actionable tips on how project managers can use AI to enhance their retrospectives, making them more effective and impactful. Rick also provides a sneak peek into future episodes where he plans to explore how AI can create continuous feedback loops to prevent recurring issues.

Rick breaks down the traditional risk management process, from risk identification and qualification to quantification and mitigation. He emphasizes the psychological challenges project managers face when considering potential risks, especially after creating an optimistic project plan. To address these challenges, Rick explores how AI can revolutionize risk management by leveraging historical data, lessons learned, and project documentation to generate dynamic and adaptive risk assessments.

In a practical demonstration, Rick uses ChatGPT to brainstorm potential risks for a hypothetical project of migrating from Salesforce to Microsoft Dynamics. He showcases how AI can drill down into specific issues, such as data compatibility, and suggest mitigation strategies. Rick also illustrates how AI can analyze project schedules and RFPs to identify variances, lessons learned, and potential risks.

Rick concludes with a vision for the future, where AI consolidates vast amounts of project information to provide actionable insights and help project managers set up effective contingencies. He encourages listeners to engage with the podcast on social media and share their feedback and suggestions for future episodes.

Tune in to learn how AI is set to transform risk management and elevate your project management skills to new heights. Don't miss this insightful episode filled with practical tips and forward-looking strategies.

Rick also explores the benefits of using ChatGPT in a conversational tone to solve technical challenges, making it easier and more intuitive than traditional search engines. Whether you’re dealing with complex data sets or looking to streamline your daily tasks, this episode is packed with valuable insights.

Tune in to hear Rick’s hands-on demonstration, personal anecdotes, and a special challenge for listeners to start automating their own workflows. Plus, don’t miss the listener feedback segment where Rick addresses questions and shares more tips on maximizing ChatGPT’s potential.

Join us on this journey to make project management more efficient and innovative with AI. Remember to reach out with your feedback and share your experiences in automating tasks using ChatGPT. Let’s drive PM productivity together!

Rick shares personal anecdotes and practical examples to illustrate how AI can enhance efficiency and creativity. He addresses common fears about AI, emphasizing the importance of practice and prompt engineering to fully leverage AI tools. Rick also recounts his experience writing books with a co-author and draws parallels to using AI for content creation, underscoring the iterative process that ensures the final output remains true to his vision.

Listeners are guided through hands-on examples, including summarizing requirements, drafting SOW introductions, and role-playing difficult conversations with stakeholders. Rick stresses the importance of validating AI-generated content and offers insights on using AI for generating project documentation, such as risk assessments and acceptance criteria.

Throughout the episode, Rick encourages listeners to experiment with AI tools, integrate them into their workflows, and use them to reduce non-value-added tasks, ultimately improving project management efficiency and effectiveness. The episode wraps up with a reminder to continuously explore and practice with AI to unlock its full potential in project management.

Tune in to "AI Driven PM" for more insights on how AI can accelerate your project management capabilities.

Rick shares his extensive background in project management, highlighting his work across various industries and his passion for the profession. He emphasizes the potential of AI to automate routine tasks, allowing project managers to focus on adding true value through forward-looking, anticipatory actions.

With AI tools like ChatGPT, project managers can now implement complex theories and methodologies that were previously too labor-intensive. Rick demonstrates how to build a personalized ChatGPT bot.

This episode is a must-listen for project managers curious about AI's practical applications. Rick provides hands-on examples and encourages listeners to experiment with AI tools to improve their workflows. Tune in for insightful discussions, practical advice, and a vision for the future of project management in the AI era.

Don't miss out—subscribe now and be part of the AI Driven PM community. Let's harness the power of AI together to elevate our project management skills and achieve extraordinary results!