Running a status update...
Running a status update...
Short, practical reads on running real projects - the stuff between the lessons.
The one-page document that authorises your project - and the five sections sponsors care about most.
It's rarely a religious war. Here's a practical way to decide based on uncertainty and cost of change.
A register nobody updates is theatre. Three habits that keep risk management real throughout delivery.
The people who quietly sink projects rarely appear on the org chart. How to find them early.
No is a legitimate project management tool. Here's how to say it without burning the relationship.
If your stakeholders are skimming (or ignoring) your status reports, the problem isn't their attention span. It's your format.
Why post-mortems fail and how to run a retro that actually surfaces useful insights.
A simple framework to decide whether to book the room or write the message - and save everyone an hour.
Stakeholders don't want status updates. They want to know whether they should be worried.
Estimates are always wrong. The skill is knowing how wrong and narrowing the cone of uncertainty.
PM Wisdom
The project health check: Green (nothing is wrong yet), Amber (something is wrong), Red (everything is wrong, please send help).