Finishing a creative project feels great, but the work is not over yet. Before you celebrate, you need a project post mortem: a structured review that turns every win and every mistake into fuel for your next launch. This is how you stop repeating errors and start compounding learnings.

What is a project post mortem and why does it matter?

A post mortem is a review of a completed project with one clear purpose: to learn and to improve. It is also the right moment to recognize the wins you or your team achieved, instead of jumping straight into the next deadline.

The idea is simple. If you don't sit down to analyze what happened, you lose the most valuable asset of any project: the lessons. And those lessons only show up clearly once the dust settles.

What is a post mortem in a creative project? It's a structured review you run a few days after delivery to identify wins, mistakes, learnings, and concrete improvements for next time.

How do you prepare an effective post mortem?

A good review depends less on talent and more on conditions. If you set the stage right, the insights almost write themselves [01:00].

• Run it within a few days of finishing the project, while everything is still fresh.
• Bring all the measurable data you have about the project.
• Keep an open mind and a positive, constructive focus.
• Always start with the wins, so the conversation begins on the right foot.

That last point matters more than it sounds. Opening with what worked sets a tone where people contribute honestly instead of defending themselves.

How do you fill the post mortem template step by step?

There is a simple template available in the resources of the class [01:30]. It is built around columns that walk you from goals to action items, so nothing important slips through.

Objectives, completion and what went well

At the top you write the project name. Then you start filling the columns from left to right.

• Objectives (measurable): write goals you can actually measure. Not abstract, not subjective. Think dates, numbers, tangible outputs.
• Was it achieved?: answer with yes, partially, or no.
• What went well: even if the goal was only partially met, something worked. Capture it here.

The key here is the word measurable. "Launch the course on the scheduled date" is measurable. "Make a great course" is not.

What went wrong, without playing the blame game

The next column is what went wrong. This is where teams often slip into finger pointing, and that kills the exercise [03:30].

Talk about processes, not people. A missed deadline is usually a planning issue, a communication gap, or a scope problem, not a personal failure. Be objective, even when the overall objective was met. Hitting the goal does not mean everything along the way was perfect.

How do you avoid blame in a post mortem? Frame every issue as a process problem, not a personal one. Ask what part of the workflow failed, not who failed.

Learnings and what to do differently

The last two columns are where the real value lives.

• What was learned: lessons from both the good and the bad. Both sides teach you something.
• What can be done differently: concrete changes for the next version of this project or for similar ones in the future.

This last question can only be answered after the project is done. It gives you a perspective you simply don't have while you are in the middle of execution.

How does a real post mortem example look?

To make it concrete, think of a project like designing an online creativity course [04:30]. The objectives could include launching on the scheduled date, building practical exercises, and creating content that applies to any profession. All of them measurable: you either launched on the date or you didn't, an exercise is either practical or theoretical.

If the launch happened on time, the what went well column might list:

• Every delivery date was respected, from proposal to scripts to drafts.
• Feedback arrived on time and at every stage, allowing agile progress.
• The production system was fast, with a strong recording rhythm.

Even so, the what went wrong column should still be filled. In this example, the team tried to cover too many exercises and struggled to decide which ones to cut. The root issue: trying to do too much from the start.

The learnings then become specific: when materials are ready on time and the production agenda is clear, edition and production speed up for everyone. And you don't need an oversized selection of exercises to deliver strong practical material.

Finally, what can be done differently opens the door to a volume two, with the exercises that didn't make the cut plus more specialized ones for an advanced audience. That is how a finished project quietly becomes the brief for the next one.

Your challenge

Download the template from the resources, fill it with your own project, and be as honest and objective as possible. If you feel comfortable, share your filled template in the comments so other creators can take insights from your process, even if their projects look nothing like yours.