Project Post-Mortem

Conduct effective project reviews with this Post-Mortem template. Analyze successes, failures, and key lessons learned to improve future projects.

Markdown
# Project Post-Mortem: [Project Name]
**Date:** YYYY-MM-DD | **Project Lead:** [Name]

## 🌟 Project Overview
*Briefly describe the project goals and whether they were met.*

## ✅ What Went Well?
- Team communication was seamless via Slack.
- The new CI/CD pipeline saved 5 hours of manual work per week.

## ❌ What Went Wrong?
- Underestimated the time needed for third-party API integration.
- Scope creep in week 3 delayed the beta launch.

## 💡 Lessons Learned
- **Planning:** Allocate a 20% buffer for technical debt.
- **Process:** Require PRD sign-off before starting development.

## 📈 Key Metrics
- **Budget:** [On track / Over]
- **Deadline:** [Met / Missed]
Preview

Project Post-Mortem: [Project Name]

Date: YYYY-MM-DD | Project Lead: [Name]

🌟 Project Overview

Briefly describe the project goals and whether they were met.

✅ What Went Well?

  • Team communication was seamless via Slack.
  • The new CI/CD pipeline saved 5 hours of manual work per week.

❌ What Went Wrong?

  • Underestimated the time needed for third-party API integration.
  • Scope creep in week 3 delayed the beta launch.

💡 Lessons Learned

  • Planning: Allocate a 20% buffer for technical debt.
  • Process: Require PRD sign-off before starting development.

📈 Key Metrics

  • Budget: [On track / Over]
  • Deadline: [Met / Missed]

How to use this template

  1. 1

    Copy the Markdown

    Click the Copy button above to put the full template on your clipboard.

  2. 2

    Paste into your editor

    Paste into VS Code, Obsidian, the mdkit editor, or any Markdown editor. The template renders cleanly in any GFM-compatible viewer.

  3. 3

    Fill in your content

    Replace the placeholder text with your own. Delete sections you don't need — the template is a starting point, not a contract.

  4. 4

    Export or share

    Commit to Git, export to HTML or PDF, or paste into your team's wiki.

What it solves

Repeating mistakes is costly. A Post-Mortem template solves this by structuring the reflection process after a project, ensuring that both successes and failures are analyzed to improve future execution.

Key features

  • Objective overview of project goals
  • Analysis of what went well and what didn't
  • Actionable lessons learned
  • Review of key metrics (Budget, Timeline)

Pro tips

  • ›Conduct the session in a 'blameless' manner; focus on processes, not people.
  • ›Schedule the post-mortem while the project is still fresh in everyone's mind.
  • ›Ensure lessons learned are actually applied to the next project's planning phase.

Related templates

Project README

Use this standard Project README template to document your software. Includes sections for installation, features, tech stack, and usage instructions.

API Documentation

Create clear API documentation with this Markdown template. Define endpoints, parameters, authentication methods, and response examples for developers.

Changelog

Keep your users informed with this Changelog template. Document project updates, bug fixes, and new features in a clear, chronological format.