View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Starfish Retrospective |  DevOps Blameless Postmortem |  DevOps Incident Command |  Operations Learning Review |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. | 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 | Low | Medium | Medium | Medium |
Timedifferent | 45-90 min | 30-90 min | As needed | 1-3 h |
Participantsdifferent | 4-12 | 3-12 | 4-15 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Postmortem Doc, Action Items, Timeline | Incident Log, Action Tracker, Stakeholder Updates | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | Site Reliability EngineeringIncidentLearningReliability | IncidentOperationsReliability | LearningRetrospectiveIncidentOperations |