Every project ends eventually. Some hit their goals, some fall short, and many land somewhere in between. What an organization does in the weeks after a project wraps up has a lot to do with how its next one goes.
A post-mortem is a structured look back at what happened, why it happened, and what the team should carry forward. Done well, it turns experience into lessons the whole organization can use. Done poorly, or skipped entirely, it lets the same mistakes repeat.
Over my career, I have found that the teams that improve fastest are the ones that make this kind of review a habit.
Review the Wins, Too
Most organizations hold post-mortems only when something goes wrong. That’s a missed opportunity.
Successful projects have just as many lessons, and they are often harder to see. A strong result can hide a near miss, a lucky break, or a process that only worked because one person stepped in at the right moment. Reviewing successes helps a team see which parts of the result came from good planning and which came from good fortune. That distinction matters the next time around.
Keep the Focus on Decisions and Process
The quickest way to ruin a post-mortem is to turn it into a search for someone to blame. Once people feel exposed, they stop sharing what really happened, and the review loses its value.
The better questions are about the system around the work. What information did the team have at each stage? Where did communication break down? Which assumptions turned out to be wrong, and why did they seem reasonable at the time?
People usually make mistakes for understandable reasons. Finding those reasons is how an organization prevents the next one.
Hold It While Memories Are Fresh
Timing matters. Details fade quickly, and within a few weeks people start to remember a cleaner version of events than the one they lived through. A review held soon after a project closes captures the real sequence of decisions, including the uncomfortable parts.
It also helps to hear from people at every level of the project. Senior leaders see the strategy. The people closest to the work often see the problems first.
Write Down What You Learned
It’s easy to forget a conversation, so you should make sure to write down the lessons from a post-mortem in plain language, stored where people can find them, and reviewed before similar work begins. If that doesn’t happen, the organization will lose the institutional memory of the lesson and can easily make the same mistake again.
End With a Next Step
Every review should end with a short list of specific changes and one person responsible for each. If it doesn’t, a post-mortem turns into a discussion that makes everyone feel better and changes nothing. One or two concrete changes that actually get made are worth more than a long list of good intentions.
Leaders Set the Tone
Teams take their cues from leadership. When a leader openly talks about his or her own misjudgments during a review, everyone else feels free to be candid. When a leader treats every setback as the team’s failing, people learn to hide problems.
Candor has to start at the top.
Organizations that keep learning from their own experience build an advantage that grows over time. A good post-mortem is one of the simplest ways to build it.
Elliott Broidy is a serial entrepreneur, investor, and philanthropist, and Chairman and CEO of Broidy Capital Holdings, a family office specializing in AI-driven public safety software.