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 Assumption Surfacing |  Facilitation Consensus Workshop |  Facilitation Alignment 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 30-240 min | 45-90 min | 1-3 h | 1-2 h |
Participantsdifferent | 1-6 | 2-8 | 5-30 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Assumption List, Critical Assumptions, Learning Plan | Consensus Clusters, Theme Titles, Priority Areas | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | AssumptionsRiskDecisionDiscovery | FacilitationConsensusWorkshopAlignment | AlignmentStakeholdersStrategyFacilitation |