View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Fault IsolationHypothesis-Driven TroubleshootingAlignment MappingStakeholder Salience Model
| Criterion |  Engineering Fault Isolation |  Engineering Hypothesis-Driven Troubleshooting |  Facilitation Alignment Mapping |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | 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 systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-180 min | 30-240 min | 1-2 h | 60-90 min |
Participantsdifferent | 1-6 | 1-6 | 4-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Alignment Map, Open Issues, Decision Questions | Salience Diagram, Strategy per Class |
Tagsno overlap | TroubleshootingDiagnosisEngineering | TroubleshootingProblem solvingDiagnosis | AlignmentStakeholdersStrategyFacilitation | StakeholdersFacilitationAlignmentGovernance |