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 |  Decision Making Delphi Method |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
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 knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 30-240 min | 1-4 Wochen | 60-90 min |
Participantsdifferent | 1-6 | 6-30 Experten | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Expert Forecast, Consensus Range, Assumption Notes | Salience Diagram, Strategy per Class |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ForecastingExpertsDecisionStrategy | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
