View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:A3 Problem SolvingFault IsolationStakeholder Salience ModelHypothesis-Driven Troubleshooting
| Criterion |  Operations A3 Problem Solving |  Engineering Fault Isolation |  Facilitation Stakeholder Salience Model |  Engineering Hypothesis-Driven Troubleshooting |
|---|---|---|---|---|
Purposedifferent | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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 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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 45-90 min | 30-180 min | 60-90 min | 30-240 min |
Participantsdifferent | 2-5 | 1-6 | 3-6 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Salience Diagram, Strategy per Class | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary |
Tagsno overlap | LeanProblem solvingCoachingOperations | TroubleshootingDiagnosisEngineering | StakeholdersFacilitationAlignmentGovernance | TroubleshootingProblem solvingDiagnosis |