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 |  Facilitation Lean Coffee |  DevOps Incident Timeline Analysis |  Facilitation Fishbowl Discussion |
|---|---|---|---|---|
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 a group without a fixed agenda needs to get into useful conversations quickly, Lean Coffee structures the start around interests rather than a presentation. The group itself negotiates which topics get time first and which wait. | For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable. | When a controversial topic needs depth and discipline at the same time, Fishbowl Discussion makes the structure of the conversation transparent. The format keeps the core small enough for real dialogue and open enough for controlled turnover. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 30-90 min | 30-90 min | 60-180 min | 45-90 min |
Participantsdifferent | 3-12 | 3-20 | 3-10 | 8-80 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Prioritized Topics, Discussion Notes, Action Items | Incident Timeline, Evidence Log, Delay Analysis, Improvement Actions | Discussion Insights, Observed Tensions, Follow-up Questions |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | FacilitationAutonomyDialogue | IncidentTimelineSite Reliability Engineering | FacilitationDialogueLarge group |