1 / 5
When a postmortem is written and reviewed in a Google Doc or Confluence page without a live meeting, this is described as:
-
-
-
-
The postmortem is conducted in a shared doc — participants contribute asynchronously, reading and commenting in their own time.
2 / 5
When team members leave feedback on a postmortem document over a 48-hour window rather than in real time, the comments are described as:
-
-
-
-
Comments are asynchronous over 2 days — this gives participants in different time zones equal opportunity to contribute without a synchronous meeting.
3 / 5
When multiple engineers add their perspective to the sequence of events during an incident in the same document, the timeline is described as:
-
-
-
-
The timeline is collaboratively edited — each contributor adds what they observed from their area, creating a comprehensive shared picture.
4 / 5
When postmortem follow-up tasks are created and assigned to owners in a project tracking tool, they are said to be:
-
-
-
-
The action items are assigned in Jira — linking postmortem outcomes to trackable tickets ensures follow-through and accountability.
5 / 5
When the meeting facilitator records a short video summarizing the postmortem findings for stakeholders who weren't involved, this is described as:
-
-
-
-
The postmortem summary is recorded as a Loom — async video allows clear explanation of complex findings without scheduling another meeting.