Are you working from home? Use Virsas to communicate with your colleagues.

Incident postmortem

Incident postmortem

Importance of incident postmortem process

As your systems grow in scale and become more complex, failure is inevitable. However, incidents are also a learning opportunity. By conducting an incident postmortem, you have a chance to discover vulnerabilities, decrease the time to resolution and mitigate repetitive incidents. But not every postmortem is equal.

The Incident Postmortem Service is a specialised Virsas tool that allows you to create a blameless process. This process brings a team together to take an in-depth look at an incident and figure out what happened. The deeper look can be achieved by reconstruction of the timeline and planning out actions needed to mitigate future issues.

The value of effective blameless postmortems

• Create a healty culture between teams

• Do not allow the fear of blame to increase the chance of ignoring incidents

• Increase communication and support

• Create always improving culture

Team management

There are two ways to create a team. One is from the main page of the incident postmortem service. The second one is from the team management page located at the top right corner. You can create as many teams as you wish with any number of members. This way, each team can have its list of incident postmortems.

Access of team members

Members of a team can access, manage and read the incidents of the group. Only an administrator can add or remove team members. The read and write access is based on the role assigned to each user and can be found in the user list.

Creating an incident

Within each team, you can create any number of incidents. The incident should contain an issue description, the resolution and who was impacted by the event the most. When you create the incident board, you can start the blameless postmortem meeting.

Blameless postmortem process

After you create the postmortem, you should add all attendees of the meeting. Then the timeline should be filled out too. Do not forget. This is the blameless process, and you should not use any names in this list. Try to use "we" as a team instead. In the end, outline actions the team needs to take to mitigate the risk of this incident happening again.

Importance of incident postmortem process

As your systems grow in scale and become more complex, failure is inevitable. However, incidents are also a learning opportunity. By conducting an incident postmortem, you have a chance to discover vulnerabilities, decrease the time to resolution and mitigate repetitive incidents. But not every postmortem is equal.

The Incident Postmortem Service is a specialised Virsas tool that allows you to create a blameless process. This process brings a team together to take an in-depth look at an incident and figure out what happened. The deeper look can be achieved by reconstruction of the timeline and planning out actions needed to mitigate future issues.

The value of effective blameless postmortems

• Create a healty culture between teams

• Do not allow the fear of blame to increase the chance of ignoring incidents

• Increase communication and support

• Create always improving culture

Team management

There are two ways to create a team. One is from the main page of the incident postmortem service. The second one is from the team management page located at the top right corner. You can create as many teams as you wish with any number of members. This way, each team can have its list of incident postmortems.

Access of team members

Members of a team can access, manage and read the incidents of the group. Only an administrator can add or remove team members. The read and write access is based on the role assigned to each user and can be found in the user list.

Creating an incident

Within each team, you can create any number of incidents. The incident should contain an issue description, the resolution and who was impacted by the event the most. When you create the incident board, you can start the blameless postmortem meeting.

Blameless postmortem process

After you create the postmortem, you should add all attendees of the meeting. Then the timeline should be filled out too. Do not forget. This is the blameless process, and you should not use any names in this list. Try to use "we" as a team instead. In the end, outline actions the team needs to take to mitigate the risk of this incident happening again.