Why do perfectly logical, well-researched project plans still fail to win people over? It's one of the most frustrating forms of project failure—not a broken schedule or a blown budget, but a smart solution that nobody trusts. Kim and Kate dig into that exact problem, exploring decision-making, risk management, and team performance through the lens of one hard-earned leadership lesson: being right is not enough. If you've ever done everything "to the T" and still hit resistance, this conversation is for you.

In this episode, Kim and Kate welcome Noel Nicole Ransom—VP of Implementation, PMP, Lean Six Sigma Master Black Belt, educator, speaker, and founder of Sigma Certify—for a wide-ranging conversation about project leadership and career advancement. Noel has led complex enterprise implementations, organizational change efforts, and strategic transformation initiatives, and now coaches professionals on bridging the gap between certification and real influence. The topic matters because so many capable project managers get stuck being seen as schedule-checkers rather than leaders, and that perception ceiling caps both their impact and their careers.

This episode explores the throughline that credibility, not correctness, is what actually moves projects forward. Noel explains that organizations run on trust rather than logic, which means a technically perfect plan can still stall if people don't feel included in how it was built. From there, the conversation moves into what Noel calls the shift from "note takers" to "progress makers" — PMs who stop documenting problems and start solving them. She offers a simple framework for unresolved roadblocks: everyone needs an owner, an action, and a date, or it can't actually be managed. The discussion also covers how to work with resistant stakeholders by treating pushback as concern rather than defiance and how leadership conversations require starting with understanding before persuasion, since executives are rarely trying to win an argument—they're trying to get to clarity.

1. Treat every unresolved roadblock as incomplete until it has an owner, an action, and a date—vague status updates don't count as progress.
   
   

2. When a stakeholder resists, get curious about the underlying concern instead of pushing harder on your rationale; questions like, "What concerns do you have?" or, "What are you seeing that we're not?" tend to open doors that arguments close.
   
   

3. When bringing ideas to leadership, come with a rough draft or "prototype" rather than an open-ended question—it invites collaboration instead of putting the entire burden of thinking on the other person.
   
   

4. Resist the instinct to arrive with every answer buttoned up; asking thoughtful questions early, framed the right way, builds far more trust than appearing to have it all figured out.

Closing Reflection

The project managers who build lasting influence aren't the ones with the most airtight plans—they're the ones who build trust one honest conversation at a time. Curiosity over certainty, progress over perfection, and quiet obstacle-removal over box-checking.

• PM Happy Hour Membership: pmhappyhour.com/membership

• PM Happy Hour Facebook Page

• Noel Nicole Ransom's website: noelnicole.com

• Noel on LinkedIn

• Sigma Certify

• Book: Never Split the Difference by Chris Voss and Tahl Raz

Ever worked on a project that felt like a complete disaster... only for leadership to call it a huge success?

In Part 2 of our Mr. Beast series, Kim and Kate dig into the reported chaos behind Beast Games—from weather disasters and safety concerns to unhappy contestants, lawsuits, and production challenges. But here's the twist: despite all the problems, does the sponsor spin it as a win? If they did - would they be 'right?'

This episode explores project sponsors, stakeholder management, risk management, and one uncomfortable truth many project managers eventually learn: success is often defined by the people funding the project—not the people doing the work.

Kim and Kate unpack what happens when ambitious goals collide with reality, why sponsors often see projects differently than project managers, and why writing your own project post-mortem may be one of the most important leadership skills you can develop.

Grab a drink and join us.

Quotes from the Episode

"Imagine that guy pouring down rain. He's in ankle deep water holding a 240 volt line over his head thinking, well, at least I'm getting paid for this." — Kate

"Watch out for fixes that move the problem instead of solving it." — Kim

Practical Takeaways

1. When project scope or scale increases dramatically, bring in people who have experience operating at that level.

2. Challenge proposed solutions by asking whether they solve the root cause or simply move the problem elsewhere.

3. Escalate business-level risks back to leadership when leadership made the decision to accept those risks.

4. Build post-mortems that document both successes and failures—not just one side of the story.

5. Tailor project communication to sponsor priorities while still surfacing risks clearly and consistently.

Closing Reflection

A project can be operationally messy and still be considered a success by its sponsors. The question isn't just whether a project succeeded—but whose definition of success ultimately mattered.

🔗 Links & Resources Mentioned

• PM Happy Hour Membership: pmhappyhour.com/membership

• PM Happy Hour Facebook Page

• Folding Ideas — Why Was I Invited to Beast Studios?

• Rolling Stone article by Stephen Essarch: A Fyre Fest Feeling Inside the Chaos of Mr. Beast's New Reality Show

• KSNV article by Minx and Lau: Las Vegas Staff Say Mr. Beast Should Be Blacklisted, Cite OSHA, Medics Set for Failure

Ever worked with a stakeholder who changes direction faster than your project plan can keep up? Then this episode may feel a little too familiar.

Kim and Kate dive into the rise of Mr. Beast and the making of Beast Games through a project management lens—not to critique content creation, but to examine what happens when vision outpaces execution. From sponsor behavior and scaling challenges to agile gone sideways, they unpack the risks of massive ambition without the systems to support it.

If you've ever managed shifting priorities, difficult stakeholders, or a project that seemed to grow by the hour, this conversation will hit home. Grab a drink and join us for a fascinating look at project sponsors, leadership, and what real-world project management can learn from internet-scale production.

🎙️ Spicy Quotes from the Episode

"Those poor people. Those poor people. I feel so bad." — Kate

"This has to be a textbook case of the absolute worst project sponsor I have ever seen." — Kim

Key Concepts & Takeaways

The Sponsor Shapes the Project
Kate frames Mr. Beast not as a creator but as a project sponsor. Great sponsors create alignment; difficult ones can unintentionally create chaos, rework, and burnout.

Scale Changes Everything
What works at small scale may not work as it scales up - in this case, scaling from Youtube videos to a massive $100m production involving thousands of participants and multiple organizations. Scaling requires stronger processes, decision making, and management support - not just bigger budgets.

Empathy Matters in Project Management
Kate repeatedly returns to the human side of projects: behind every schedule slip or scope change are real people doing the work.

Practical Takeaways

• Evaluate sponsor behavior early, not just project requirements.

• Reassess processes when projects scale dramatically.

• Governance doesn't slow decisions - it can help speed them and ensure your project can effectively absorb changing priorities.

• Consider the human impact of ambitious timelines and scope changes.

• Distinguish between innovation and avoidable chaos.

🔗 Links & Resources Mentioned

• Folding Ideas video: "Why Was I Invited to Beast Studios?" (https://youtu.be/0dwagg5wYY4?si=wNMmjhncv06AqUul)

• Project Management Happy Hour Website

• PM Happy Hour Membership