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 Stakeholder Mapping |  Facilitation Consensus Workshop |  Facilitation Decision Jam |
|---|---|---|---|---|
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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-240 min | 60–90 min | 1-3 h | 60-90 min |
Participantsdifferent | 1-6 | 2-8 | 5-30 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Stakeholder Map, Engagement Plan, Risk Notes | Consensus Clusters, Theme Titles, Priority Areas | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | StakeholdersAlignmentFacilitationChange | FacilitationConsensusWorkshopAlignment | FacilitationDecisionProblem solvingWorkshop |