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 Consensus Workshop |  Decision Making RAPID |  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 a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. | 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-240 min | 1-3 h | 45-90 min | 60-90 min |
Participantsdifferent | 1-6 | 5-30 | 3-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Consensus Clusters, Theme Titles, Priority Areas | RAPID Role Map, Recommendation, Decision Log | Salience Diagram, Strategy per Class |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | FacilitationConsensusWorkshopAlignment | DecisionRolesGovernance | StakeholdersFacilitationAlignmentGovernance |