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
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Paper session grid with two time blocks, three rooms, colored session cards and an open topic pool.
Facilitation
Barcamp
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
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 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.When many people can contribute knowledge and the flow should stay open, Barcamp provides a framework for self-organized sessions. The format channels energy without defining the content too narrowly in advance.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
30-240 min60-90 minHalber Tag bis 2 Tage1-3 h
Participantsdifferent
1-64-1015-2005-30
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryProblem Cluster, Prioritized Challenge, ExperimentSession Board, Session Notes, Community LearningsConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
FacilitationDecisionProblem solvingWorkshop
FacilitationLarge groupLearning
FacilitationConsensusWorkshopAlignment
Add more methods