View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Blameless Postmortem |  Agile Starfish Retrospective |  Agile Start Stop Continue |  Operations Learning Review |
|---|---|---|---|---|
Purposedifferent | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-90 min | 45-90 min | 30-60 min | 1-3 h |
Participantsdifferent | 3-12 | 4-12 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection | LearningRetrospectiveIncidentOperations |