
A quick introduction to the course, what you can expect and a little about who I am.
Post mortems give us an opportunity to learn from what has happened. This makes them an incredibly powerful tool to drive positive change.
In this quick win learn about the 5-Why's, a tool that helps you get to the bottom of what happened.
Get an overview of the processes we'll cover to conduct a post mortem.
Before you get started with a post mortem taking a moment to define what your objectives are, and what will be included, is important.
In this stage you'll be gathering all the data you can about what happened, including interviewing folks, system logs, tickets and more.
Here you'll learn how to create a system diagram in draw.io, a free tool similar to Visio or Lucidchart.
In this quick win learn two methods for creating a timeline - in a text document and in a mapping tool.
Once you've got all the data gathered, you'll need to sit down and analyze it. From there, you'll come up with insights as to what happened, as well as action items on how to improve.
Here we'll walk through a post-mortem document created in Confluence to better understand what can go into them and what they look like.
This meeting provides a forum to discuss the event, and learn with the team.
Once you've analyzed your data, the last step is to implement the improvements and action items you've identified.
Here we'll wrap up the section.
Building a culture of improvement can be challenging - but is incredibly rewarding. Here we'll kick off this section on how to get one started.
It can be challenging to convince people post-mortems are needed. This lecture covers some ways you can convince others they are.
Building any habit is challenging, but performing regular post mortems both makes them easier to do and helps your team grow.
Post mortems are intended to help avoid mistakes or amplify growth, so keeping blame out of them is critical. Learn more about why in this lecture.
Understanding that blame doesn't have a place in a post mortem is one thing - writing one without it is another. Learn how here.
Learn why celebrating success is an important part of helping an organization build a culture of improvement.
Wrap up everything you've learned here
Post mortems are an incredibly important tool in project management, incident response and other areas of business. They not only help groups avoid negative problems, but also enhance positive outcomes by digging in and learning what works.
Additionally, post mortems are not a way to blame a team or an individual - they're a way for the group to improve and do better. Cultivating a blame-free environment when conducting post mortems is critical to their success.
This course is designed around two main sections:
Section 1 - How to conduct a post mortem
This section covers how to run a post mortem successfully, and includes things like:
Defining what will be included in your post mortem process
How to collect information - including identifying who should be involved and what information you need
Analyzing what you find - Drawing conclusions from all that data
Conducting a post mortem meeting - getting everyone together to brainstorm how to do better next time
Implementing improvements - How you'll take what you've learned and make it real
Section 2 - Cultivating a culture of improvement
This section focuses on how to help your team focus on improving, and moving away from blaming. Lectures include:
Building buy in - Convincing others that post-mortems are important can be hard, start small and build out.
Making a habit of post mortems - They shouldn't be only only on special occasions, do them for every project to help build a habit
Blameless - post mortems aren't meant to blame, instead they're meant to help us all do better
Who Should Enroll
This course is meant for anyone who might be involved in a post mortem, or expected to run one. Examples of roles that tend to do this include:
Software Engineers: Analyze system failures and identify improvements
Systems Managers: Determine the cause of system faults and avoid them
Analysts: Figure out why a project is successful and help others do the same
Customer Support : Pull apart an escalation and avoid them
Project Managers: Ensure project closure with effective post-mortems, especially following unexpected challenges.
Scrum Masters: Augment your toolkit with practices that foster team growth and efficiency.
Why Choose This Course:
Every project ,incident, escalation, failure, success (and more!) should be analyzed to see why it happened. You should choose this course because you want to learn from success (and failure), and because you want your team to focus on improving - not blame.