View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Facilitation Lean Coffee |  Facilitation Fishbowl Discussion |
|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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. | 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 |
Timedifferent | 30-240 min | 30-90 min | 45-90 min |
Participantsdifferent | 1-6 | 3-20 | 8-80 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Prioritized Topics, Discussion Notes, Action Items | Discussion Insights, Observed Tensions, Follow-up Questions |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | FacilitationAutonomyDialogue | FacilitationDialogueLarge group |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
