View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Lean Coffee |  DevOps Incident Command |  DevOps Game Day |  Facilitation Fishbowl Discussion |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | 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 | Low | Medium | High | Medium |
Timedifferent | 30-90 min | As needed | Halber Tag | 45-90 min |
Participantsdifferent | 3-20 | 4-15 | 5-20 | 8-80 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized Topics, Discussion Notes, Action Items | Incident Log, Action Tracker, Stakeholder Updates | Simulation Notes, Gaps List, Updated Runbooks | Discussion Insights, Observed Tensions, Follow-up Questions |
Tagsno overlap | FacilitationAutonomyDialogue | IncidentOperationsReliability | ResilienceOperationsIncident | FacilitationDialogueLarge group |