Bad stuff sometimes happens in software. How you learn from postmortems is what really matters.

Use of technology is exploding, which means there are more teams building software each year that passes. If you’re one of the designers, engineers, or product managers who’s involved in creating software products, you’re probably aware that it’s not a matter of if your product goes down, but when. No matter how much think you about reliability, issues happen.
The only failure is a failure to learn. Of course it’s bad news when your product goes down and impacts customers, but if done correctly, every event can become a learning opportunity to improve your team and processes. Postmortems (or post-mortem/post morem) are at core of every incident. It’s a process that involves analysis, discussion after an event has taken place to get to the root cause of an issue, learn from it, and make sure it doesn’t happen again.
Below is a template that can help you easily share what happened, why, how it impacted customers, and lessons learned for the future for next steps to improve.

Start building your internal knowledge base today

Fewer repetitive questions for you and faster answers for your team.

We guarantee you’ll be hooked.

Create your knowledge base