Most project post-mortems end the same way: a thoughtful document, nods and agreements in the final meeting, and a folder nobody opens again.
It isn't for lack of good intentions. Useful things do come out of the conversation. But the team is already on to the next project, and a list of observations has no natural place to land. "Communicate earlier with stakeholders" is true, and rarely gets put into practice.
We see this most often with teams that run lean, where the person who just finished the project is already starting the next one. Here is what makes the difference.
Capture it while it's happening. Keep a running note through the project of decisions, surprises, and what you'd do differently. At the end you're editing, not trying to remember.
Choose three. A post-mortem with twenty findings produces zero changes. Pick the three takeaways that would be most impactful for the projects that follow.
Turn each one into a specific change. "Scope was unclear" becomes "add an out-of-scope list to the project template and review it at kickoff." If you can't name the exact tool or process to update, the lesson is half-baked.
Put it where the next project starts. Think of a packing list. When you forget a charger, you add it to your packing checklist for next time, not your travel journal. Lessons belong in the kickoff checklist, the project template, and the scoping questions - the tools you actually reach for.
Make the change in the meeting. A to-do for later competes with the next project, and the next project wins. Open the checklist or template during the review and update it in the moment.
The goal isn't a better post-mortem document. It's a better next project.
Start with a pre-mortem, too.
The same discipline works in reverse. A pre-mortem, a practice popularized by psychologist Gary Klein, takes about thirty minutes before the work begins. Picture the project having gone badly, then ask each person to write down what went wrong. Because the failure is imaginary, people say the things they would otherwise hold back: the team is stretched, the data is messier than anyone admits, the sponsor is hard to reach.
It doesn't have to sound alarming. Many teams frame it as "what could get in our way?" and keep it to the core project team. The payoff comes at the end of the project. The pre-mortem list becomes a checklist for the post-mortem: which of these risks showed up, which didn't, and what do we change next time? Keep both in one document, and the two exercises inform each other. This exercise can also feed your project risk tracking log.
At Clearly Consulting, we take what we learn from each project and build on that, so one engagement shapes how we run the next. Contact us for a no-pressure discussion about your project.
