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 Stakeholder Mapping |  Facilitation Storytelling |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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 initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 30-240 min | 60–90 min | 45-120 min | 1-2 h |
Participantsdifferent | 1-6 | 2-8 | 1-6 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Stakeholder Map, Engagement Plan, Risk Notes | Narrative Outline, Key Message, Story Arc | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | StakeholdersAlignmentFacilitationChange | CommunicationNarrativeStakeholdersFacilitation | AlignmentStakeholdersStrategyFacilitation |