Do Pre-Mortems For Your Projects

When projects end poorly, some companies run a post-mortem process.

The post-mortem process usually goes through a root cause analysis exercise for why the project went poorly.

For example, maybe there was an issue integrating with another team or a third-party vendor that took longer than expected and jeopardized the timeline.

There’s usually also a section for what went well during the project.

Most teams don’t run a pre-mortem process before the project begins.

It’s the same thing as a post-mortem, but instead of being retrospective, it’s proactive.

At the beginning of a project, ask yourself and your team what could result in the project ending poorly.

Take action items to mitigate these risks.

Also, ask your team what must happen for the project to succeed.

This quick and inexpensive exercise can provide valuable insights early and align everybody on the desired outcomes.


Like what you've read?

If you're an engineering leader or developer, you should subscribe to my 80/20 DevOps Newsletter. Give me 1 minute of your day, and I'll teach you essential DevOps skills. I cover topics like Kubernetes, AWS, Infrastructure as Code, and more.

Not sure yet? Check out the archive.

Unsubscribe at any time.