Blameless postmortems have a distinct vocabulary. Learn the collocations for conducting postmortems, identifying systemic issues, capturing lessons learned, and turning them into action items.
0 / 5 completed
1 / 5
The SRE team committed to ___ a blameless postmortem within 48 hours of every P1 incident.
Conduct a blameless postmortem is the professional collocation used in SRE and DevOps culture. 'Hold' implies a meeting; 'run' is informal; 'perform' is theatrical. 'Conduct' frames the postmortem as a structured professional activity with defined steps.
2 / 5
Rather than assigning blame, the team focused on ___ the root causes of the outage.
Identifying root causes is the standard postmortem collocation. 'Finding' is too casual; 'discovering' implies surprise; 'uncovering' suggests hidden intent. 'Identifying' is the precise analytical term used in incident review frameworks.
3 / 5
The postmortem revealed several ___ issues in the deployment pipeline that had been overlooked.
Systemic issues is the canonical collocation in blameless postmortem language. 'Fundamental' and 'core' describe importance rather than organizational spread; 'deep' is informal. 'Systemic' specifically signals that the problem exists across the system, not just one individual's action.
4 / 5
By the end of the session, the team had agreed on five ___ items to prevent recurrence.
Action items is the standard postmortem collocation for concrete tasks assigned after analysis. 'Follow-up items' is broader; 'remediation items' is used in security contexts; 'task items' is redundant. 'Action items' is the universal professional term for assigned next steps.
5 / 5
The facilitator reminded everyone that the goal was to ___ lessons learned, not to assign fault.
Capture lessons learned is the idiomatic phrase in retrospective and postmortem language. 'Document' is also correct but more mechanical; 'collect' implies physical items; 'gather' is vague. 'Capture' suggests active recording of insight before it is lost.