You’re staring at the dashboard. The burndown chart is flatlining. The key metric that was supposed to go up and to the right is, in fact, going down and to the left. You feel that familiar knot in your stomach. It’s time to write the weekly status report, and the status is “bad.”
The temptation is to soften the language. To write that things are “trending behind schedule” or that you’ve “encountered some headwinds.” This is a mistake. Vague reporting on a failing project doesn’t protect you; it just delays the inevitable, painful conversation.
There’s a better way. Instead of documenting the problem after it’s too late with a post-mortem, you need to diagnose it while there’s still time to act. You need a Mid-Mortem Report.
Stop Writing Autopsies. Start Writing Diagnoses.
A post-mortem is an autopsy. The project is dead, and the team gathers to figure out what killed it. The goal is learning for the future.
A mid-mortem is a diagnosis. The patient is on the operating table, and you are the surgeon explaining the situation to the family. The goal is to present a clear picture of the problem and propose a treatment plan to save the patient. It’s a tool for immediate course correction, not a history lesson.
This report reframes bad news from a confession of