Advertise on podcast: PM Debate Podcast

Back in 2018, Mary Elizabeth and I recorded an episode of PM Debate on a question that’s aged better than most: is a candidate’s current salary a real signal of whether they’ll succeed as a project manager? I argued yes. Not because it’s fair, it’s not, but because the job market had already become too noisy to screen any other way. Once hiring stopped being local and started being global, recruiters lost the built-in filter that geography and reputation used to provide. Compensation became a blunt but practical proxy. Mary Elizabeth argued no, and made the harder case. Current salary reflects history, not fitness, a project manager coming from a lower cost-of-living market, a different industry, or a season of deliberately choosing less responsibility will always look “wrong” on paper by that measure alone. She also pointed to something a lot of PMs still don’t clock: the wage gap doesn’t just create inequity, it launders that inequity forward every time compensation is used to screen the next role. We went back and forth on it in the full episode, including a story about an offer that came in 40% higher than expected, and one that came in 50% lower than a VP title implied. The debate holds up. If anything, the industry has moved further in Mary Elizabeth’s direction since we recorded it, more jurisdictions have banned the salary-history question outright. This was one of the last conversations we recorded in that run of the show. We may bring PM Debate back in a different format down the line, but for now, the archive is worth revisiting on its own merits. Where do you land: is current salary a useful filter, or a lazy one? 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

Throwback Thursday. This one comes from the PM Debate archive, back when Mary Elizabeth and I used to pick a question and argue it out from opposite corners. Episode 41 was personal for me, because I argued the side I actually disagree with. Early in my career, a manager pulled me aside after watching me work for a couple of hours. He asked if I was the type of person who worked the middle of the room at a party or the type who stood off to the side, talking to one or two people. Before I could answer, he told me the job needed someone who wanted to be the life of the party. There was no room for shy people in our business. That comment stuck with me for twenty years. So when we built this episode, I took the side of that manager, not because I believe it, but because the bias behind it is real and worth naming out loud. The Tension For the motion (me): * Project management runs on communication, visibility, and the ability to read a room fast * Introverts are often read as shy, aloof, or even arrogant, and that perception becomes a barrier before the work even starts * Stakeholders are already resistant to change. A project manager who reads as disengaged makes that resistance worse * Introverts who succeed usually do it by building extroverted skills on top of who they are, not by waiting for the world to understand personality types Against the motion (Mary Elizabeth): * Introverts prepare more thoroughly. They think through what could go wrong before it does, which makes them naturally strong at risk planning * They listen more than they speak and ask clarifying questions, which slows a team down just enough to make better decisions * They tend to be the more creative thinkers on a team, particularly when a problem needs a solution nobody has tried yet * The traits that get mistaken for weakness (patience, listening, depth of thought) are often exactly what a project needs under pressure The Line That Still Hits “There is no room for shy people in our business.” I heard that in my twenties from a manager who meant it as career advice. A decade of leading transformations later, I still think about how wrong, and how common, that advice was. Why This Still Matters The bias hasn’t gone anywhere. We still promote the person who fills a room over the person who reads it. We still mistake volume for leadership and hesitation for weakness. Meanwhile the project manager who prepares harder, listens longer, and asks the question nobody else thought to ask is usually the one keeping the whole thing from falling apart. The real answer was never in the title of the episode. It was in the tension itself. You don’t fix introversion. You learn when to step outside of it, and you build a team and a culture that doesn’t force everyone to perform the same way to be taken seriously. Final Thought I didn’t stop being an introvert. I learned to get over myself when the room needed it. That’s a different thing entirely from becoming someone else. Where do you land? Does your organization actually make room for both types of leaders, or does it just say it does? Listen to the full episode, questions and closing statements included, wherever you get your podcasts. 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

No paycheck, no performance review, no real consequence for walking away. On paper, managing volunteers sounds like the harder job. Mary Elizabeth and I debated it, and the real question turned out to be less about volunteers and more about something every PM eventually has to face: how much of your leverage was ever real in the first place. The Tension Mary Elizabeth argued for the motion. Her case: * With no paycheck at stake, there’s nothing stopping a frustrated volunteer from simply disengaging, and that changes the whole management equation * A volunteer project almost never sits at the top of someone’s priority list, so when work, family, or life gets in the way, the project loses * Passion-driven teams invite ego and politics in a way that can turn toxic fast, especially when people are fighting for a cause instead of a paycheck I argued against it. My case: * The idea that paid staff comply because of pay doesn’t match reality. Most PMs, even ones with formal authority, get results through influence, not leverage * Ego and political infighting are just as present in the corporate world. People undermine each other for position all the time * Comparing volunteer projects to staff projects is really comparing different terrain, not different difficulty. It’s like saying finance is harder to manage than construction The Line That Still Hits A volunteer leader, dealing with a stakeholder who wouldn’t let an issue go, got the perfect deadpan response from someone higher up the chain: “Don’t worry, we’ll make sure we don’t give this volunteer a raise, so his pay will go from zero to zero next year.” Why This Still Matters Most PMOs today run on teams that barely resemble a clean staff hierarchy anyway. Matrixed reporting lines, cross-functional squads, people who answer to three priorities before they answer to yours. The volunteer dynamic isn’t a niche case anymore. It’s closer to the default. Final Thought Whether someone’s on payroll or not, authority was never the thing doing the work. Influence was. Which is actually harder for you to lead: a team that’s paid to show up, or a team that’s only there because they want to be? 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

Some phrases get used so often they stop meaning anything. “Speaking truth to power” is one of them. Mary Elizabeth and I picked it apart in this throwback, and the debate ended up being less about courage and more about something most PMs never talk about openly: who actually has the standing to say the hard thing, and who’s just going to get hurt for trying. The Tension Mary Elizabeth argued for the motion. Her case: * Delivering uncomfortable news, unrealistic timelines, scope conflicts, resource overload, is squarely inside the PM’s job description * Done well, it protects the project and the sponsor’s own interests, even when they don’t want to hear it * There’s a method to it: know the roadmap, know what keeps leadership up at night, and know when to stop talking I argued against it. My case: * “Every” is doing too much work in that sentence. Plenty of PMs never get close enough to power to speak to it * A lot of organizations run like small dictatorships regardless of what country they sit in, and the cost of speaking up doesn’t always justify the act * Even the people who’ve earned the access often lack the skill to do it well, and ego gets tangled up in what people call “the truth” The Line That Still Hits My closing argument came down to this: speaking truth to power assumes you have exclusive access to the truth. Most of the time you don’t. Collaboration and joint problem-solving get you further than the hero moment of telling leadership what they need to hear. Why This Still Matters This one lands differently depending on where you sit in an organization right now. If you’re newer, it’s a reminder that access to power is earned, not assumed. If you’re senior, it’s a check on ego, the belief that because you’re closest to the work, you’re the only one who sees it clearly. Final Thought Speaking truth to power isn’t the same as doing the right thing, and it isn’t the same as being honest. We tend to collapse all three into one virtue. They’re not. What’s your read: is this a skill every PM needs, or a privilege some PMs earn? 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

We’ve spent two episodes on this from the candidate’s seat. Episode 36 asked if taking a job you’re not ready for is a disaster. Episode 37 asked if being overqualified quietly sinks you. This throwback flips the chair. Now you’re the hiring manager, and there’s no perfect-fit candidate in the pile. Do you take the one who has too little or too much? That was the motion Mary Elizabeth and I closed the series with, and listening back, it’s less about resume than it is about which risk you’re actually willing to manage. The Tension On one side, the overqualified hire looks like the safer bet, until it isn’t. * They come with habits from other jobs, some useful, some not * Resentment about “settling” can turn into cynicism, and cynicism spreads across a team fast * You may be investing in someone who leaves the moment the market improves On the other side, ruling out the overqualified candidate can cost you just as much. * You lose someone who could mentor and elevate everyone around them * Experienced hires often ramp up faster, which is real money saved * You assume desperation or a flight risk when the real reason might be a deliberate career change The Line That Still Hits Mary Elizabeth put it best: hiring managers can feel a bit like Goldilocks. This one’s overqualified, that one’s under-qualified, and you can never quite find the one that’s just right. Most managers default to “safe” under-qualified, trainable, cheap. But safe isn’t the same as smart. The Real Question This isn’t really about who checks more boxes. The real question is: Are you hiring for the task list in front of you, or the bench strength you’ll need two years from now? Those are two different hiring decisions wearing the same job posting. Before You Decide If you’re staring down this exact choice, ask yourself: * Am I retraining a skillset, or retraining an attitude? * Will this hire bring energy into the room, or resentment? * Can I actually offer growth here, or am I just filling a seat? * Am I solving for today, or building my succession pipeline? What This Means for Candidates If you’ve ever been passed over for being “too much” or “not enough” for a role, know it usually has nothing to do with your resume. It’s a manager weighing a risk they can’t fully see from the other side of the table. Final Thought There’s no universally right answer here, and that’s the point. Hire under-qualified and you’re betting on growth. Hire overqualified and you’re betting on impact. The mistake isn’t picking one versus the other but it’s not knowing which bet you’re actually making. 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

We continue to deal with a job marketplace that is seeing a certain degree of volatility. This throwback debate from back in 2018 is still relevant today. Is accepting a position you’re overqualified for setting yourself up to fail? It’s the flip side of the coin from Episode 36. The more I listen back, the more I realize over-qualification isn’t really about skill level at all. It’s about ego, expectations, and whether you can let go of who you used to be. The Debate On one side, taking a job below your qualification level can quietly wreck you. * Employers assume you’re either uncommitted or about to bolt * You get paid less because “you’ll take anything anyway” * Every piece of work gets a second look, hunting for the incompetence they expect to find On the other side, writing off overqualified candidates costs you just as much. * You lose someone who could teach and elevate the whole team * You miss people who’ve deliberately chosen stability over another rung of the ladder * You assume desperation when the real reason might be a career change, family, or burnout The Line That Still Hits Almost twenty years ago I found myself as an accidental entrepreneur leading a startup after making the switch from a corporate job. In a startup, you’re a jack of all trades. You meet clients, deliver the work, answer the phone, take out the trash. Nothing is beneath you. That’s the attitude I carried back into the corporate world when I returned. Once the ego is out of the way, the question of whether you’re “overqualified” stops mattering. What matters is whether you’re still delivering value. The Real Question This isn’t really about qualifications. Everyone eventually knows more than the job in front of them at some point in their career. The real question is: Are you taking the role to learn, teach, or grow? Or are you just parking yourself somewhere comfortable? There’s a difference, and it shows up fast. Four Questions Before You Say Yes If you’re weighing a role that feels like a step down, ask yourself: * Can I actually succeed here? * Will this let me differentiate myself? * Will I learn something, or teach someone? * Will I still enjoy the work? If most of the answers are no, you’re not stepping into a growth opportunity, you’re just marking time. What This Means for Hiring Hiring managers have their own version of this dilemma. Do you bring in the candidate who checks every box, or do you worry they’ll be bored, underpaid, and gone in six months? The honest answer is: it depends entirely on how the expectations get set on day one, not on the resume itself. Final Thought Overqualified isn’t a red flag, but it’s a question. The candidates who fail aren’t the ones with too much experience, they’re the ones who never let go of who they used to be. 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

Another throwback debate that still challenges how we think about hiring, and ourselves Is accepting a job that one is under qualified for a disaster in the making? That was the focus of the motion from a few years ago. The more I listen to this episode of the PM Debate Podcast, the more I realize this isn’t just a hiring question. It’s a leadership question, a self-awareness question, and a career-defining decision. The Tension On one side if you step into a role you’re not ready for, you risk everything. * Losing the trust of your team * Failing to deliver when it matters most * Damaging your credibility before you’ve even built it In project environments where timelines, budgets, and outcomes matter that risk is real. On the other side if you only take roles you’re fully qualified for you * You stop growing and stay in the shallow end. * You repeat what you already know. * You miss the very opportunities that shape your career. The Line That Still Hits Early in my career, I used to ask hiring managers: “Do you want someone with one year of experience repeated fifteen times… or someone who actually knows how to do the job?” It worked, but looking back (I’ll be honest) that confidence came with risk. Sometimes it worked because I grew into the role, sometimes it worked because I got lucky. That’s the part we don’t talk about enough. The Real Question This isn’t about being 100% qualified, after all, no one is. The real question is: Are you stretching or are you stepping in over your head? There’s a difference. Three Checks Before You Say Yes If you’re considering a role that feels like a stretch, ask yourself: * Will this team trust me enough to follow me? * Can I actually deliver what this role demands? * Will leadership believe in me when things get tough? If the answer to any of these is no, you’re probably going beyond stretching yourself to gambling with the role or relying a bit too much on luck. What This Means for Hiring Hiring managers face the same dilemma. We often wonder if we should play it safe and hire that fully qualified candidate or take a chance on someone who could become exceptional. The problem is most systems are built to filter out potential before it ever gets a chance. Final Thought The best careers aren’t built by playing it safe, but they’re also not built on blind risk. Success in a role and in a career is built in that uncomfortable space between where you’re not quite ready but you’re ready enough. 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

When a crisis hits, everyone wants quick action. But fast without structure isn’t decisive, it’s just chaotic. Back in 2017, Mary Elizabeth and I debated a motion that sits at the intersection of two very different disciplines: “The project management framework and its principles are ill suited for managing a crisis.” It sounds provocative, and it was meant to challenge assumptions and explore the topic. The Core Debate The argument for the motion: * A crisis isn’t a project. It doesn’t get “created”, it erupts. * The scale of coordination required goes far beyond typical stakeholder management. * First responders, government leaders, community organizations, and the public don’t make a project team. That’s a different operating model entirely. * PM gave us a strong framework for recovery, but response? That belongs to a different discipline. The argument against the motion: * Crisis management and project management share more DNA than people admit. * Risk planning, communication frameworks, and resource distribution. All of these core PM tools are directly applicable under pressure. * The real criticism isn’t the framework, It’s the misapplication of it. * Agile proved PM can move fast when the context demands it, crisis is no different. The clear tension to consider is this: PM is a powerful tool but only if you know which problem you’re holding it up against. Why This Still Matters in 2026 Crises haven’t gotten simpler. If anything, they’ve multiplied. Organizational shutdowns, supply chain collapses, reputational emergencies, and geopolitical disruption all impact program delivery. In most organizations, when a crisis hits, one of two things happens: * Someone pulls out a project plan and tries to run the response like a workstream. * Or nobody pulls out anything, and it’s improvised chaos from minute one. Both are wrong. The real question this episode was pointing at is all about the application of the framework. 3 Questions for Today’s Leaders * Does your organization have a crisis response capability, or just a project plan it hopes will stretch far enough? * When the last disruption hit, did PM discipline help or slow things down? * What’s the line in your context between “crisis response” and “recovery project” and who owns each side of it? 🎧 Episode 35 is live now. 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

Project teams often say they want transparency but executives often say transparency has limits. So which is it? This week’s throwback episode from the Project Management Debate Podcast tackles a question that sits right at the intersection of leadership, ethics, and strategy: Do project team members and key stakeholders deserve full disclosure at all times? It’s a deceptively simple question. But once you dig into it, the answer becomes far more complicated. The Case for Full Disclosure One of the strongest arguments for transparency is simple: withholding information usually backfires. When project leaders hold back critical details, three things tend to happen: * Suppliers misunderstand the real requirements.Organizations sometimes conceal details to gain negotiating leverage. But suppliers eventually uncover the truth and by then, trust has already eroded. * Teams lose morale and motivation.Artificial deadlines or hidden constraints can make work feel impossible. When teams sense the goalposts aren’t real, they disengage. * Relationships break down.When risks or major changes are hidden, teams feel excluded from solving the problem. By the time the truth surfaces, it’s often too late to recover. The central argument here is not just ethical but also practical. Information gaps create risk. The Case Against Full Disclosure But there’s another side to the debate. Organizations operate in competitive environments. Sometimes sharing everything is simply not responsible leadership. Consider a few common realities: * A new product launch must remain confidential to avoid tipping off competitors. * A merger is underway but cannot be disclosed until agreements are finalized. * An internal restructuring could disrupt morale if shared prematurely. In these cases, leadership isn’t deciding whether transparency is good, they’re deciding when transparency becomes possible. In business, timing matters as much as truth. The Real Question: What Does “Full Disclosure” Actually Mean? In the discussion, a more nuanced idea emerges: Full disclosure doesn’t mean sharing everything with everyone immediately. It means sharing the right information with the right stakeholders at the right time. That’s where leadership judgment comes in. Project professionals often find themselves navigating gray areas between transparency, trust, and strategic confidentiality. A Final Thought In the closing remarks, one example stands out: sandbagging. * A team member thinks a task will take two hours, but to avoid risk, they say one day. * The manager reports one week. * Leadership tells the board one year. This exaggeration illustrates what happens when trust disappears. When people don’t feel safe sharing the truth, the entire system distorts reality. Once that happens, no project plan can save you. The Debate Continues So here’s the question for you: Should project teams always receive full disclosure? Or is selective transparency sometimes the smarter leadership choice? Reply and share your perspective. The best insights often come from the debate. 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

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 Debate The 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 2026 Look 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 them People 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 it Drop 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 practice Question 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