Episode 546: The Real Reason Project Requirements Keep Changing

About this episode

Cornelius Fichtner discusses with Lee Fischman the reasons behind changing project requirements and the influence of early product decisions.

Play audio-only episode | Play on YouTube | Play on Spotify Episode Summary Project 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.

People in this episode

Host: Cornelius Fichtner

Guest: Lee Fischman

Topics covered

• project management
• requirements change
• product management
• leadership
• project execution

Keywords

• project requirements
• change management
• product thinking
• leadership behavior
• delivery outcomes

More episodes of The Project Management Podcast

• Episode 553: Revenge of the Risk Register (Premium Preview) · May 29, 2026
• Episode 552: PMP Exam Content Outline (For Exams on or after 2026-July-09) · May 17, 2026
• Episode 551: What Movies Teach Project Managers · May 15, 2026
• Episode 550: How to Turn Chaos Into Project Clarity (Premium Preview) · April 30, 2026
• Episode 549: How to Bring Clarity to Chaotic Projects · April 4, 2026
• Episode 548: From Project Delivery to Value: How Project Managers Create Real Business Impact · February 13, 2026