PM Debate Podcast

A few years ago we tackled a question that feels even more relevant today:Is social media amplifying confirmation bias inside organizations, and quietly increasing project risk?At the time, platforms were being criticized for algorithm-driven echo chambers. The idea was simple:You like something → you see more of it.You agree with something → it gets reinforced.You never get challenged → your worldview hardens.Sound familiar?The Core DebateThe argument for the motion:* Confirmation bias affects hiring, promotion, innovation, and team composition.* Algorithms amplify what we already believe.* Less exposure to diverse thinking = higher project risk.* If your team looks and thinks like you, you may build something perfect… for yourselves.The argument against the motion:* Confirmation bias existed long before social media.* It’s rooted in background, exposure, and human psychology.* Real change happens through lived interaction, not feeds.* Social media may enable bias, but it didn’t invent it.Two sides with one uncomfortable truth: Confirmation bias is real, and in projects, it’s dangerous.Why This Still Matters in 2026Look around.* Teams cluster around shared thinking.* Leaders seek validation instead of challenge.* Escalations get framed to confirm the preferred narrative.* “Data” gets interpreted to support the already-made decision.Ultimately the project suffers quietly.Innovation dies in echo chambers, risk hides in blind spots, and dissent gets labeled as resistance.The real question isn’t whether social media causes confirmation bias but rather:What are you doing as a leader to counter it?3 Questions for Today’s PM Leaders* Do you actively invite opposing viewpoints, or just tolerate them?* Does your hiring pattern expand diversity of thought, or replicate yourself?* When new evidence challenges your plan, do you lean in, or double down?Confirmation bias isn’t just a societal issue. It’s a governance issue, a culture issue, and a leadership issue.If we don’t manage it deliberately, it becomes a hidden risk on every transformation.🎧 This week’s Throwback Thursday episode is live.Give it a listen and tell me:Has confirmation bias gotten worse or are we just more aware of it?Project Management Matters is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

Are lessons learned actually… learned?Back in 2017, on the PM Debate Podcast, we tackled a question that still makes people uncomfortable:“Documenting lessons learned on projects is a waste of time.”At the time, it felt provocative and eight years later it feels current.In this episode, Mary Elizabeth and I took opposite sides of the argument.I argued for the motion, not because lessons don’t matter, but because most organizations confuse documentation with learning. We create reports, archive them, check the box… and then launch the next project as if none of it ever happened.Mary Elizabeth argued against the motion, rightly pointing out that lessons learned do matter when they’re accessible, contextual, and built into how projects actually start, plan, and execute.Here’s where we landed:📌 The biggest failure isn’t that we don’t capture lessons learned📌 It’s that organizations aren’t designed to use themPeople move on, teams dissolve, context disappears, and leadership often already knows the risks, but chooses to proceed anyway.One of the stories I share in this episode still sticks with me:A project that failed repeatedly over 15 years… with the same scope, same structure, and many of the same people involved. The lessons were written down, management just didn’t listen.So maybe the real question isn’t when we document lessons learned.Maybe it’s:* Who is accountable for acting on them?* Where do they show up in decision-making?* And what happens when they’re ignored?🎧 Throwback episodes like this remind me that tools haven’t failed us. behavior has.Curious where you land on this debate today?I’d love to hear it.Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

Corporate politics is a game every PM must play…. Or is it? This throwback episode of the PM Debate Podcast goes straight at a question most project managers quietly wrestle with, but rarely say out loud:Should project managers play corporate politics… or stay out of it entirely?In this debate, Mary Elizabeth and I take opposing sides.One argument says politics are unavoidable.If you influence without authority, you’re already in the game.You might as well learn how to play it well for the benefit of the project.The other argument says politics are pure risk.They serve egos, not outcomes.The moment a project manager gets pulled in, the project starts paying the price.What makes this episode timeless is that both positions are uncomfortable and both are real.Projects don’t exist in org charts, they exist in human systems that are messy.This isn’t a “how-to” episode, it’s a think-it-through episode.Reflection question:Have you seen a project succeed because someone navigated politics well or despite itDrop your take in the comments. I’m genuinely curious.Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

Can the PMO be both cop and advocate?This week’s Thursday Throwback takes us back to an old PM Debate Podcast episode with a question that still makes people uncomfortable:Can the PMO enforce standards and still be a trusted partner to the business?On one side: If the PMO is auditing projects, enforcing compliance, and reporting up, how can teams ever see it as an ally?On the other: If the PMO doesn’t have skin in the game, if it only reports from the sidelines, what value is it really adding?The debate wasn’t really about structure, it was about trust, value, and culture.Years later, I’m convinced this tension never fully goes away. The best PMOs don’t “solve” it, they manage it deliberately, by focusing less on policing behavior and more on helping teams win.Worth revisiting, still relevant, and still debated.👉 Listen to the throwback episode and decide where you land.Can a PMO be both, or does trying to be everything risk becoming nothing?Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

Back in 2017, on Episode 29 of the PM Debate Podcast, we took on a question that was already gaining momentum at the time:Is freelance project management just a passing fad, or is it the future of the profession?On one side, the argument was clear: globalization, offshoring, and project-based work were pushing organizations toward short-term, specialized talent. For project managers, that meant more autonomy, but also more responsibility for their own careers, finances, and long-term stability.On the other side, we challenged the assumption that freelancing is inevitable. Hidden costs, loss of institutional knowledge, confidentiality risks, and the very human desire for stability all complicate the picture. Not every organization or every professional thrives in a fully freelance model.What makes this episode worth revisiting nearly a decade later is how unfinished the debate still is. The job market may look different today, but the core tension hasn’t gone away: Who carries the risk: the organization, or the individual?Listen to the episode and decide for yourself whether the profession has proven this was a trend… or whether the jury is still out.As always, I’m curious: Has your own career moved closer to one side of this debate since 2017 or further away?Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

We love shortcuts, especially when hiring feels risky, messy, and expensive. So we lean on certifications, not as inputs, but as answers. This episode of the PM Debate Podcast takes on a belief that still shapes hiring decisions every day: that certification equals competence.What makes this debate interesting isn’t the conclusion, it’s the actual arguement.On one side:Certifications are knowledge checks, useful, even if incomplete. They can’t tell you how someone behaves when things go sideways.On the other:Certifications were never meant to predict success. They were meant to establish a baseline, and the failure is in how we misuse them.Here’s the bottom line: Most organizations don’t actually know how to assess competence.Hiring managers often default to proxies.This conversation is a reminder that real capability shows up in judgment, context, and execution, none of which fit neatly on a resume.🎧 Listen to Episode 28 if you want a sharper lens on:* Hiring risk vs. hiring comfort* Why project failure gets oversimplified* What competence really looks like in practiceQuestion to listeners:What’s the most misleading signal you’ve seen used to judge a project manager?Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

Trust is easy to talk about but it is much harder to define and even harder to decide what actually earns it.In this throwback episode of the PM Debate Podcast, we revisited a deceptively simple motion:Competence is more important than loyalty when it comes to trusting team members.On the surface, it sounds academic but in practice, it’s deeply personal and operationally dangerous to get wrong.On one side of the debate:* Competence creates predictability.* Predictability creates trust.* If someone can’t deliver, no amount of good intent saves the team downstream.On the other:* Competence can be taught.* Loyalty can’t.* A disloyal team member doesn’t just fail, they choose to break trust.The discussion quickly moved beyond theory into the real questions leaders face:* Would you rather manage underperformance or disloyalty?* Is loyalty to the organization different from loyalty to a leader?* Is trust built through results… or relationships?* Is it fair to expect both?What makes this episode endure isn’t the answer, it’s the tension. Every hiring decision, every promotion, and every team reset forces leaders to weigh these two forces, often with incomplete information.🎧 Listen to the episode and join the debate.Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

Micromanagement might be the most disliked word in leadership.It’s usually associated with distrust, control, burnout, and people heading for the exits. And yet… projects still fail every day because leaders are too distant, too hands-off, or too disengaged.That tension is exactly what we debated years ago on the PM Debate Podcast in an episode titled:“Hail to the Micromanager, Without Whom No Project Gets Done.”Listening back now, what stands out isn’t how old the debate sounds, it’s how current it still feels.What This Episode Was Really AboutThis wasn’t a defense of bad micromanagement, it was a challenge to a lazy assumption:👉 Is all close oversight harmful or are we confusing micromanagement with leadership?On one side: Projects fail when leaders are absent. High-risk, fast-moving work doesn’t allow for “figure it out as you go.” Detail, presence, and course correction matter.On the other: True micromanagement kills initiative, slows delivery, demotivates teams, and drives talent away. It turns project managers into task-doers instead of leaders.Both arguments are valid and that’s the point.The Line Most Organizations Still MissMicromanagement is not the same as being detail-oriented, bad micromanagement is about control. Good oversight is about clarity, timing, and responsibility.Projects don’t need hovering, they do need leaders close enough to see risk early and act with intent.That distinction is still misunderstood and still causing damage.🎧 This episode is worth revisiting with today’s lens.Reflection question:Where have you seen “hands-off leadership” do more harm than good?Let’s reopen the debate.Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

Back in 2017, Mary Elizabeth and I recorded a Project Management Debate episode that still feels current.The motion was simple but controversial: “Percent complete is not a good indicator of project status and progress.”Eight years later, I’d argue this debate matters even more. Not because percent complete is always wrong but because the definition of success has always been greater than one variable.Most executives don’t actually want percentages, they want confidence. They want to know:- Are we on track in reality, not in a spreadsheet?- What’s at risk that isn’t obvious yet?- Where will this slip hurt the business?Percent complete feels precise but sometimes this is a trap. When schedules are poorly structured, when tasks are vague, when optimism creeps in (and it always does), percent complete becomes a comfort metric. It reassures without informing. It smooths over uncertainty instead of exposing it.On the other side of the debate, there’s a fair counterpoint: With strong planning, disciplined breakdowns, and the right reporting models, percent complete can be useful.This episode explores judgment and whether we’re honest with ourselves and stakeholders about what we really know.🎧 I’m resurfacing this PM Debate throwback because the question still deserves airtime.So let me ask you: Do you trust percent complete on your projects? Or do you rely on something else to tell you the real story?Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

Every project leader eventually faces the same uncomfortable moment:A project is off the rails. Now what?This week’s PM Debate episode dives into one of the hardest judgment calls in the profession:👉 Is it better to bail out and restart a troubled project, or to double down and push through the pain?It’s a deceptively simple question with massive consequences for scope, cost, culture, and credibility.In this episode, Mary Elizabeth and I take opposite sides of the argument, because both perspectives are true depending on the situation.The Case for Restarting (Mary Elizabeth’s Argument)Some projects fail not because the idea is wrong, but because the execution has drifted so far off course that minor corrections won’t fix anything.Restarting can bring:* A renewed planning process* Clearer visibility into risks that derailed the first attempt* Permission to re-evaluate non-performing resources* A stronger team with a fresh start* The discipline to stop throwing good money after badIt’s the project equivalent of pulling the car out of the ditch instead of turning the wheel harder.The Case for Doubling Down (My Argument)But there’s a darker side to restarts. If organizations restart too quickly, they create:* A culture of false starts* Teams that lose momentum* Project managers who avoid working through difficulty* Executives who become risk-averse* A delivery ecosystem afraid to push past discomfortSometimes the hard part isn’t a signal to quit, sometimes it’s the gateway to the real work.Momentum matters, team learning matters, and finishing what you start matters.When Do You Choose Which?In the open discussion we tackled the questions leaders actually face:* How do you define a project that’s truly “in trouble”?* Which warning signs matter and which are noise?* When does sunk-cost thinking blind us?* How should PMOs use stage gates to reduce bailout risk?* What role should sponsors play in deciding direction?* And the biggest one: When is it actually harder to finish than to restart?This episode isn’t about giving the “right” answer, it’s about sharpening judgment.Great project leaders don’t just follow process, they read the world their project is operating in and choose intentionally.👉 Listen to the full debate here.Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

Most organizations who agree that they need a PMO are far less likely to agree on how to build one.This week’s throwback episode of the PM Debate Podcast tackles a question that still divides executives, consultants, and PMO leaders today:Should companies outsource PMO setup to expert consultants or trust internal staff to build it?On one side of the debate:* External consultants bring experience, objectivity, industry knowledge, and credibility.* They’ve done this before, know the pitfalls, and can accelerate structure and delivery.On the other side:* Internal staff know the culture, the politics, the personalities, and the reality behind the org chart.* They’re embedded, invested, and far better positioned to tailor a PMO to actual needs.It’s a debate that reveals something deeper about organizational maturity, leadership expectations, and what it really takes to build a PMO that lasts.In this episode, Mary Elizabeth and I explore:* What skills truly matter in a PMO setup* Whether PMOs can be built “out of the box”* The risks of outsourcing vs. the risks of going internal* What executives consistently misunderstand about PMO budgets* Why capability handover is the make-or-break factor* And how organizational size and industry complexity change the equationIf your organization is considering a new PMO, or rethinking the one it has, this debate will give you the clarity (and honesty) that most conversations avoid.Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

Every PMO leader has lived some version of this story:A strategy consultant walks in with a slide deck full of vision statements, transformation pathways, and a list of 70+ “strategic initiatives” that all need to be delivered in the next 12–18 months.Then they walk out and the PMO is left holding the bag.In this week’s Throwback Thursday PM Debate Podcast, Mary Elizabeth and I revisit one of the most controversial topics we ever tackled:“Blame it all on the strategy consultant, why PMOs fail.”👉 I argue for the motion. Strategy consultants often underestimate organizational capacity, dilute accountability, and hand over beautifully written plans that violate basic laws of physics. (82 initiatives in 13 months? With 213 people? Come on.)👉 Mary Elizabeth argues against. Organizations should know better. If you outsource your thinking, accept generic reports, and never push back, isn’t that on the client?Together we explore the bigger questions:* Is the failure in the idea, the plan, or the people delivering it?* Who owns accountability when the strategy thinkers disappear before the strategy doers show up?* Are PMOs set up to succeed… or set up as the fall guys?* And how do we stop the blame game between strategy and execution?If you’ve ever inherited a strategy that looked great in theory but impossible in practice, this episode will hit close to home.🎙️ Listen to the archived episode here. After you listen, I’d love to hear your take:Who’s really to blame when strategy looks perfect on paper but collapses in delivery?Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

This week on Standards Week, we’ve been talking about foundations, structure, and what helps organizations deliver consistently.So for Throwback Thursday, I’m revisiting an episode from 2017 that looks at the other side of the coin: pace.The question we debated was simple but uncomfortable:“Must organizations change fast… or die?”In this episode, Mary Elizabeth and I take opposite sides of the argument: speed vs. stability. We explore the tension leaders still wrestle with today:* How fast is too fast?* When does “adapt or die” become harmful?* Can organizations slow down change without falling behind?* Does rapid change erode excellence?* Are people resisting… or being resilient?* What’s the difference between deliberate action and knee-jerk reaction?Seven years later, these questions feel even more timely.🎧 Listen to the 2017 episode: “Organizations Must Change Fast or Die”Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

Have you every heard this question?“Can someone with no project management background successfully run a PMO?”Half of all PMOs fail within three years, at least that’s what some studies claim. Many of those failures could be traced back to leadership. But what kind of leadership matters most?In this PM Debate throwback, Mary Elizabeth and I went head-to-head on one of the most controversial questions in our field: “An organization that appoints a PMO leader with no experience in project management and no track record in PMOs is doomed to fail.”Mary Elizabeth argued for the motion, experience is essential.I argued against, leadership, influence, and organizational fit matter more.We explored:* Whether industry and cultural understanding can compensate for limited PM knowledge* The difference between technical expertise and leadership capability* Why some PMOs thrive under unconventional leaders while others collapse under expertsIt’s a conversation that’s just as relevant today, especially as PMOs evolve to balance firefighting and foundation-building.🎧 Listen to the full episode: PM Debate Podcast – “An Inexperienced PMO Leader Is Doomed to Fail”#CtrlAltPMO #PMODebate #Leadership #ProjectManagement #PMOPodcast #RapidStartPMOThanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

In this week’s PM Debate throwback, we explore a provocative question:👉 Can projects succeed even when companies have bad or failing strategies?🎙️ I argue that project success must be tied to strategy otherwise, we’re just delivering activity, not value.🎙️ Mary Elizabeth counters that strong project delivery can be the saving grace, even in companies with poor strategic direction.From mismatched metrics to misunderstood impact, we tackle:* What “success” really means in project management* How PMs should act when strategy is unclear or flawed* Why good projects don’t always mean good outcomes“You can finish on time and on budget but still deliver the wrong thing.”🔁 Give it a listen. Then join the debate. Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

Should Project Managers Be Responsible for Benefits Realization?Some say no, it’s outside the PM’s scope and sits firmly in the hands of program and portfolio leaders.Others argue, if the PM doesn’t ensure value is delivered, who will?In this archived episode, we go head-to-head on one of the most misunderstood expectations in project leadership.Mary Elizabeth argues for the motion: the PM is not responsible.Philip argues against it: the PM must step up to own value.🎧 Listen and decide for yourself💬 Then join the conversation: Should benefits realization be in the PM’s job description? Get full access to Project Management Matters at philipdiab.substack.com/subscribe

There’s one question that still sparks real debate: If you have project managers, do you really need change managers?This week’s throwback episode of the PM Debate Podcast dives straight into it.🗣️ I argued for the motion:“Organizations that employ project managers have no need of change managers.”🎙️ Mary Elizabeth took the other side, challenging that idea from the perspective of change maturity, people dynamics, and organizational readiness.Why this debate still matters:In one corner: The argument that project management = change management– Every PM is a change agent by default– Most of the job is stakeholder engagement, expectation-setting, and alignment– Adding a change manager risks duplicating roles or undermining authorityIn the other corner: The argument that change management is its own discipline– Not all change is formally “a project”– Change managers focus on the people side of change– When organizations lack maturity, change managers bridge critical gapsQuestions we explore:* Is “change management” just another name for good project management?* Should every PM also be a change expert, or is that unrealistic?* What happens in orgs where no one owns the people side of transformation?* Is change management leadership, or is it a role?Whether you’re leading a transformation or building a PMO from scratch, this episode challenges how we think about who is really responsible for making change stick.🎧 Listen to the full episode and join the debate📍 Let me know in the comments where do you stand on this one?Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

This debate episode is one of our most downloaded, and for good reason.We go head-to-head on a question every PMO leader has faced:Is firefighting a breakdown of planning and culture?Or is it a skill leaders must embrace in a high-stakes, high-pressure world?🎧 PM Debate: Firefighting vs. Project ManagementNow streaming again for #ThrowbackThursday. This topic is all about culture because firefighting doesn’t just happen, it’s taught, rewarded, and normalized.What behaviors is your organization reinforcing?And what would it take to break the pattern?👇 Join the debate in the comments.#PMDebate #CtrlAltPMO #ProjectManagement #WorkCulture #Leadership #Firefighting #ThrowbackThursday #PMOThanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

In this week’s PM Debate Podcast throwback, we go head-to-head on a question that’s even more relevant today than when we first recorded it back in 2017:👉 “Can virtual teams ever match the effectiveness of collocated ones?”I argue for the motion.Mary Elizabeth argues against. We cover:* The role of trust, presence, and “read of the room” moments* Whether technology truly bridges the performance gap* How talent access and time zone flexibility reshape delivery* And why virtual can work but collocated still holds the edge (for some)This one will hit home for anyone managing hybrid or global teams.🎧 Listen to the episodeThen drop your take:Are virtual teams just different or inherently disadvantaged?Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe

This week’s PM Debate podcast digs into one of the profession’s biggest questions:Should every organization have a PMO?I say yes. Mary Elizabeth says not so fast. In this archived episode, we debate:* Whether PMOs are strategic necessities or expensive overhead* Why small businesses might be overspending on structures they don’t need* What it really takes to make a PMO succeed, and what makes them failWe also tackle questions like:* What is a corporate PMO, really?* Are some industries just not built for them?* Can a bad PMO do more harm than good?The debate is still just as relevant today as it was then, especially as PMOs evolve into transformation engines in a changing world.🎧 Listen to Episode #14👇 After you listen, let me know:Do you believe every organization benefits from a PMO? Are we forcing a structure where it doesn’t belong?Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work. Get full access to Project Management Matters at philipdiab.substack.com/subscribe