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 |  Engineering Fault Isolation |  Facilitation Stakeholder Mapping |  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. | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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 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 | Medium | Low | Medium |
Timedifferent | 30-240 min | 30-180 min | 60–90 min | 1-2 h |
Participantsdifferent | 1-6 | 1-6 | 2-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Stakeholder Map, Engagement Plan, Risk Notes | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | TroubleshootingDiagnosisEngineering | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersStrategyFacilitation |