Project Management Insights

Most status reports are theatre, green, green, green, until the week before launch. We look at how AI can pull honest signals from commits, tickets, calendars and chat, and turn them into an update your sponsor can actually trust. Plus the politics of telling the truth faster than your organisation is ready for.

The same project update needs to land very differently with the CEO, the engineering lead, and the client's procurement team. AI makes that translation cheap, but only if you brief it well. We cover the audience profiles, the tone controls, and the one mistake that makes every version sound the same.

Can a daily AI summary replace the morning standup? In some teams, absolutely. In others, you'd be removing the only 15 minutes of human contact left. This episode is a practical decision tree: when to drop the meeting, when to keep it, and how to design an async version that surfaces blockers instead of hiding them.

AI can replace the standup as an information ritual, but not as a social ritual. The PM's job is to know which one their team actually needs, design the async version to surface blockers rather than hide them, and keep enough synchronous human contact to preserve cohesion.

Half your team is now pair-programming with Copilot, drafting docs with Claude, and running their own little agent workflows. So what's left for the project manager? This episode maps out the parts of the role that AI compresses, the parts it amplifies, and the new responsibilities nobody put in your job description.

AI is not removing the PM role, it is changing which parts of it matter. The work the PM did out of necessity is being compressed, the work that only the PM can do is being amplified, and new responsibilities, especially around quality control of AI output, are arriving without being added to anyone's job description.

Everyone left the kickoff feeling good. The objectives were broad, the timeline looked clean, and the stakeholders were aligned, or so it seemed. Six weeks later, three departments had three different ideas of what the project was supposed to deliver. This episode traces the confusion back to a kickoff meeting that covered the slides but avoided the real conversations. Listeners learn what a project charter should lock down before work begins, why assumptions need to be surfaced and documented, and what questions every kickoff meeting must answer.

Lesson: A kickoff meeting that does not surface the hard questions, assumptions, scope boundaries, and decision rights, creates the appearance of alignment without the substance. A real charter forces those conversations before the work begins, not after the cracks appear.

The Project Files is a storytelling series from Project Management Insights. Each episode follows a real project scenario where something goes wrong, gets complicated, or almost falls apart. The stories are fictional but the lessons are real, drawn from the challenges that show up on projects every day. If you manage projects, work on them, or lead the people who do, these stories are for you.

A small request came in from a senior stakeholder. It seemed minor. The team started working on it immediately. By the time the project manager found out, two weeks of schedule had been consumed. This episode walks through what a change control process is designed to prevent and what happens without one. Listeners learn how change requests are evaluated, what an integrated change control board does, and how to say no without damaging a stakeholder relationship.

The Project Files is a storytelling series from Project Management Insights. Each episode follows a real project scenario where something goes wrong, gets complicated, or almost falls apart. The stories are fictional but the lessons are real, drawn from the challenges that show up on projects every day. If you manage projects, work on them, or lead the people who do, these stories are for you.

Halfway through the project, the third-party vendor missed a critical deliverable. The project manager had a contract, a penalty clause, and no backup plan. This episode follows the scramble to recover and the lessons learned about procurement. Listeners learn the difference between fixed-price and time-and-materials contracts, what a statement of work should include, and why vendor management belongs on the project schedule.

The Project Files is a storytelling series from Project Management Insights. Each episode follows a real project scenario where something goes wrong, gets complicated, or almost falls apart. The stories are fictional but the lessons are real, drawn from the challenges that show up on projects every day. If you manage projects, work on them, or lead the people who do, these stories are for you.

The developers thought the testers had it. The testers thought the business analysts had approved it. Nobody had it. This episode traces a project failure back to a single broken handoff and the communication gaps that made it inevitable. Listeners learn how a communications plan works, what meeting cadences protect against, and why information distribution is a discipline, not an assumption.

The Project Files is a storytelling series from Project Management Insights. Each episode follows a real project scenario where something goes wrong, gets complicated, or almost falls apart. The stories are fictional but the lessons are real, drawn from the challenges that show up on projects every day. If you manage projects, work on them, or lead the people who do, these stories are for you.

The system went live on time and on budget. Three months later, it was barely used. This episode tells the story of a project that delivered exactly what was specified but missed what the business actually needed. Listeners learn the difference between outputs and outcomes, why benefits realization belongs in the project plan, and what change management has to do with project success.

The Project Files is a storytelling series from Project Management Insights. Each episode follows a real project scenario where something goes wrong, gets complicated, or almost falls apart. The stories are fictional but the lessons are real, drawn from the challenges that show up on projects every day. If you manage projects, work on them, or lead the people who do, these stories are for you.

The client wanted delivery in 90 days. The project manager knew it was not possible but said yes anyway. This episode follows the consequences of an unachievable baseline schedule and the painful process of recovery. Listeners learn how to build a bottom-up estimate, why schedule compression techniques like fast-tracking and crashing carry their own risks, and how to have the deadline conversation before it becomes a crisis.

The Project Files is a storytelling series from Project Management Insights. Each episode follows a real project scenario where something goes wrong, gets complicated, or almost falls apart. The stories are fictional but the lessons are real, drawn from the challenges that show up on projects every day. If you manage projects, work on them, or lead the people who do, these stories are for you.​​​​​​​​​​​​​​​​