View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Hypothesis-Driven TroubleshootingStakeholder Salience ModelDecision JamDecision Rights Mapping
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Facilitation Stakeholder Salience Model |  Facilitation Decision Jam |  Decision Making Decision Rights 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. | 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 a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-240 min | 60-90 min | 60-90 min | 90-180 min |
Participantsdifferent | 1-6 | 3-6 | 4-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Salience Diagram, Strategy per Class | Problem Cluster, Prioritized Challenge, Experiment | Decision Rights Matrix, Agreement |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | StakeholdersFacilitationAlignmentGovernance | FacilitationDecisionProblem solvingWorkshop | DecisionGovernanceAlignmentResponsibility |