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 for RAPID
Decision Making
RAPID
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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 min45-90 min1-3 h60-90 min
Participantsdifferent
1-63-121-84-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryRAPID Role Map, Recommendation, Decision LogArgument Map, Evidence Gaps, Decision RationaleProblem Cluster, Prioritized Challenge, Experiment
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
DecisionRolesGovernance
SensemakingDecisionRationale
FacilitationDecisionProblem solvingWorkshop
Add more methods