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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin 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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic.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
MediumHighMediumLow
Timedifferent
30-240 min1-4 Wochen60-180 min60-90 min
Participantsdifferent
1-61-64-204-10
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryExperiment results, Decision log, Learning summaryCynefin Map, Domain-specific Actions, Sensemaking NotesProblem Cluster, Prioritized Challenge, Experiment
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
ExperimentsGrowthAnalyticsValidation
ComplexitySensemakingDecision
FacilitationDecisionProblem solvingWorkshop
Add more methods