Finishing a creative project feels great, but the work is not done yet. A project post mortem is the structured review you run right after wrapping up to capture lessons, celebrate wins, and turn experience into better future work. If you lead creative projects, design courses, or run client work, this practice is what separates one-off success from repeatable craft.

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

A post mortem is a review of a completed project with one purpose: to learn and improve. It does not matter if the project was a hit or fell short, the goal is to extract insights you can reuse next time.

It is also the moment to recognize the wins you and your team achieved. Acknowledging what worked builds momentum for the next round.

What is a post mortem in a creative project? It is a structured review held right after a project ends, focused on measurable goals, what went well, what failed, lessons learned, and what you would do differently.

When should you run a post mortem?

Timing changes everything. A few principles to keep it useful:

• Run it within a few days of finishing the project so memory stays fresh.
• Bring measurable data, not just impressions.
• Keep an open, constructive mindset.
• Always start with the wins to set the right tone.

How do you structure an effective post mortem template?

The template works as a grid: the project name on top, then rows for each objective and columns that walk you through the analysis. Each column has a specific job, and skipping any of them weakens the review.

What goes in each column of the post mortem?

Here is what each section captures and why it matters:

• Measurable objectives: concrete, not abstract. They must have a date, a number, or something tangible you can verify.
• Was it met?: three options only, yes, partially, or no.
• What went well: actions, processes, or decisions that worked. Fill this in even if the objective was missed, because something always went right.
• What went wrong: process gaps, not personal blame. The focus stays on the system, never on people.
• What was learned: the learnings extracted from both the wins and the failures.
• What can be done differently: the most important column, where you turn reflection into a plan for the next version or future projects.

Why separate "what went wrong" from "what was learned"? Because failures only become valuable when you translate them into a lesson. Without that step, you repeat the same mistakes.

The column on what to do differently is special: it can only be answered after the project is finished, and it gives you a fresh angle on decisions you made along the way.

How does a post mortem look with a real example?

To make it concrete, take the project of designing an online creativity course. The objectives were measurable: launch on a scheduled date, include practical exercises, and create content that applies to any type of professional.

Wins, failures, and lessons from the course launch

The launch hit its scheduled date, so the answer to "was it met?" is yes. What went well:

• Every delivery date was respected, from the course proposal to outlines and drafts.
• Feedback arrived on time and at every stage, which kept progress agile.
• The production system was highly agile, allowing recordings at a strong pace.

What went wrong, even with a successful launch, is that the team tried to cover too many exercises and had to discard some, struggling to decide which ones to keep. The root cause was wanting to fit too much from the start.

The lessons were clear: when materials are ready on time and the production agenda is well defined, editing, production, and creative work all speed up. Also, you do not need an oversized selection to deliver solid practical material.

What can be done differently next time?

The forward looking move is a volume two. The exercises that did not make the cut, combined with new specialized ones, could become a second course aimed at a more advanced experience level. That is how a learning turns into a roadmap.

How to make your post mortem honest and useful?

A few habits keep the exercise valuable:

• Be objective with both wins and failures, do not take feedback personally.
• Talk about processes, never about people. This is not a blame game.
• Use measurable data wherever possible to avoid vague conclusions.
• Share your filled template with peers, even if their projects differ from yours, because insights travel across disciplines.

Download the template, fill it with your own project, and if you feel comfortable, drop it in the comments. Other creators will pick up reflections that apply to their own work, and you will sharpen yours by putting it out there.