Episode 548: From Project Delivery to Value: How Project Managers Create Real Business Impact
Episode SummaryProject work dominates how organizations grow, transform, and compete, yet many projects still fail to create meaningful impact. This conversation examines why delivering plans, schedules, and outputs no longer defines success for project managers. As expectations shift toward value creation and strategic impact, the role of the project manager expands beyond execution into leadership, influence, and decision-making. Antonio Nieto-Rodriguez, a leading authority on project leadership and organizational transformation, explains how organizations have become project-driven and what that shift demands from those leading initiatives.The discussion highlights how the growth of transformation initiatives, accelerating change, and the increasing use of artificial intelligence reshape project work. Projects now compete for attention and resources in environments overloaded with initiatives, often leading to fragmentation and poor outcomes. The conversation explains why improving methods alone does not raise success rates and why leadership sponsorship, organizational focus, and clear prioritization matter more than ever. Particular attention is given to the tension project managers experience when they remain measured on time and budget while being asked to lead change and create business value. A central theme of the episode is the gap between delivering project outputs and realizing value. The conversation shows how value emerges through intentional benefit definition, stakeholder involvement, and ongoing dialogue with leaders about outcomes that matter to the organization. Rather than reporting task completion or schedules, project leaders must connect work to measurable improvements such as revenue growth, cost reduction, time to market, or sustainability outcomes. The episode closes with practical guidance on asking better questions, co-creating benefits with stakeholders, and positioning project managers as leaders who drive impact in project-driven organizations. This interview was originally published on The PM Podcast. |
Posted on: March 16, 2026 01:32 AM
| Permalink |
Comments (1)
Episode 546: The Real Reason Project Requirements Keep Changing
Episode SummaryProject requirements rarely change because teams lack discipline. More often, change starts long before a project manager ever joins the work. Early product decisions define priorities, assumptions, and constraints that quietly shape delivery outcomes. In this conversation, Cornelius Fichtner speaks with Lee Fischman about why project managers so often inherit projects that feel impossible and how product thinking influences what gets built, how success is defined, and how much flexibility exists when reality shifts. The discussion connects product management, project execution, and leadership behavior, showing how unclear intent, untested value assumptions, and early commitments lead to ongoing requirement changes later in delivery.Lee explains how product managers focus on deciding what should be delivered, while project managers focus on ensuring delivery within cost, schedule, and scope. Problems arise when those roles disconnect or when success criteria shift as teams learn more about users, markets, and constraints. The conversation highlights practical concepts such as pre-mortems, working backward from outcomes, recognizing bias in decision-making, and treating plans and even large programs as experiments. These ideas apply in both adaptive and predictive environments, especially when teams face pressure to commit to dates that leaders do not fully understand. The episode also addresses communication habits that reduce surprises, including writing to clarify thinking, making assumptions visible, and choosing meetings deliberately instead of by default. Lee discusses why plans calcify, how bias and sunk costs reinforce rigid thinking, and why leaders play a critical role in preventing projects from locking into failing paths. The discussion closes with actionable takeaways focused on humility, communication, and creating environments where learning happens early enough to influence outcomes rather than after delivery. This interview was originally published on The PM Podcast. |
Posted on: February 09, 2026 07:19 PM
| Permalink |
Comments (1)
Episode 544: The Four Pillars of Project Success
Categories:
Project Success
Categories: Project Success
Episode SummaryProjects rarely fall apart because of tools or templates. They struggle because leaders lack clarity, adaptability, awareness, and strong communication habits. Author and coach Scott Barnard joins Cornelius Fichtner to share a practical leadership framework built on four pillars that help project managers guide their teams through turbulence. Drawing from more than three decades of recovering troubled initiatives, Scott explains how these pillars help teams anticipate disruption, reduce stress, and keep moving toward meaningful outcomes. His experience spans major global programs, complex software projects, and large organizational transformations, all of which reveal a consistent pattern: when leaders strengthen these four pillars, chaos loses its grip and teams deliver more confidently.The conversation moves through vision, adaptability, situational awareness, and communication using real project stories, including cost concerns raised in kickoffs, strike risks, shifting customer demand, global holidays, pandemic disruptions, and even ancient ruins discovered during metro construction. Along the way, Scott shares how leaders use future scenarios, modular roadmaps, and structured decision habits to stay ahead of chaos instead of reacting to it. He also describes how clear communication and consistent meeting rhythms stabilize teams, reduce confusion, and accelerate decisions. No magic wand required, although a good sense of humor certainly helps when the preposterous future shows up anyway. Listeners walk away with simple and actionable steps. These include crafting a succinct mission statement, defining goals and objectives early, building alternative roadmaps, using the OADA loop (observe, analyze, decide, act), and maintaining clear, concise, and consistent communication. Scott’s examples show how small leadership habits ripple across a project, reducing stress, improving teamwork, and creating delivery environments where success is far more likely than chaos. This interview was originally published on The PM Podcast. |
Posted on: January 15, 2026 04:09 AM
| Permalink |
Comments (1)
Episode 543: Catch Project Trouble Early and Protect Your Delivery
Episode SummarySubtle problems often start long before a project shows obvious signs of distress. Leaders feel the pressure to deliver momentum, teams shift toward activity over outcomes, and stakeholders slowly fade as competing priorities pull them away. In this conversation, Matthew Oleniuk brings his experience from overseeing large public sector projects and highlights seven early indicators that signal when a project is heading toward trouble. He explains why these issues are easy to ignore, how they quietly compound over time, and why strong leadership vigilance matters more than any dashboard color. He also describes how patterns like output beating outcome, performance theater, and risk box ticking show up in real projects and why they are so harmful when left unchallenged.Matthew shares examples from large government programs, multi-year initiatives, and everyday delivery environments to show how project culture and infrastructure can create blind spots. He also explains why people naturally lean toward positive reporting and how even well intentioned leaders slip into habits that mask the truth. The discussion closes with practical guidance on rebuilding transparency, protecting meaningful testing, anchoring to clear outcomes, and strengthening leadership behaviors. Matthew emphasizes that project drift, unclear roles, weak accountability, stakeholder fade, and generic risk lists are not signs of bad people but signs of systems that need stronger leadership habits. His final recommendation centers on objective self-assessment so project managers can identify trouble early and adjust course with confidence. This interview was originally published on The PM Podcast. |
Posted on: January 14, 2026 04:54 AM
| Permalink |
Comments (1)
Episode 542: Inside PMBOK Guide 8: What Project Managers Must Know
Categories:
PMBOk 8
Categories: PMBOk 8
Episode SummaryThe eighth edition of the PMBOK Guide has dropped and it represents another significant evolutions in PMI’s standards. This conversation takes listeners directly inside its development. Jesse Fewell, who chaired the PMBOK Guide 8 effort, offers a detailed look at how tens of thousands of data points, practitioner feedback, and extensive review cycles shaped the newest edition. He explains how the standard brings greater clarity, a more intuitive structure, and practical guidance that aligns with the way projects actually unfold rather than how we might idealize them on paper. This episode also highlights major updates, including a fully revised definition of a project and a modernized view of project success that emphasizes value, perception, and consensus across stakeholders, even when budgets or schedules are challenged.Cornelius and Jesse walk through the table of contents, from the ANSI-accredited standard to the PMBOK Guide and supporting material. Jesse explains why certain long-standing elements remain, why others changed, and how the team reduced duplication while strengthening universal principles such as value focus, sustainability integration, and accountable leadership. He also shares behind-the-scenes details about the double-blind volunteer structure, how review teams handled more than fifteen thousand comments, and why principles were streamlined from twelve to six for clarity and usability. The Sydney Opera House example even makes an appearance to show how a "failed" project can still be a success when the delivered value resonates strongly with stakeholders. The conversation also touches on predictive, adaptive, and hybrid development approaches, how performance measurement now includes both delivery and value components, and that the new edition does not introduce new lifecycle models. Jesse provides context on the inclusion of emerging AI concepts in an appendix, noting that rapid industry changes made it impossible to codify specifics in a lasting way. The episode closes with updated definitions for "project" and "project management," which reflect a more modern understanding of temporary initiatives, context, and value creation. This interview was originally published on The PM Podcast. |
Posted on: January 13, 2026 12:43 AM
| Permalink |
Comments (1)
