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 Storytelling |  Delivery Communication Plan |
|---|---|---|---|
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 an insight needs to have an effect, storytelling translates dry facts into a comprehensible development. It combines context, tension, and consequence into a form that people remember and pass on more easily. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 30-240 min | 45-120 min | 45-90 min |
Participantsdifferent | 1-6 | 1-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Narrative Outline, Key Message, Story Arc | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | CommunicationNarrativeStakeholdersFacilitation | CommunicationStakeholdersDeliveryPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
