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 Alignment Mapping |  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. | 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 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. | 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 | 45-90 min | 1-2 h | 60-90 min |
Participantsdifferent | 1-6 | 2-8 | 4-12 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Assumption List, Critical Assumptions, Learning Plan | Alignment Map, Open Issues, Decision Questions | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | AssumptionsRiskDecisionDiscovery | AlignmentStakeholdersStrategyFacilitation | FacilitationDecisionProblem solvingWorkshop |