methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration of the Lightning Decision Jam working structure.
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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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
MediumMediumMediumLow
Timedifferent
30-240 min30-90 min1-3 h60-90 min
Participantsdifferent
1-61-65-304-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryDecision Tree, Option Map, Assumption ListConsensus Clusters, Theme Titles, Priority AreasProblem Cluster, Prioritized Challenge, Experiment
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
DecisionTreeOptions
FacilitationConsensusWorkshopAlignment
FacilitationDecisionProblem solvingWorkshop
Add more methods