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 hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Alignment Mapping.
Facilitation
Alignment 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 early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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
MediumLowMediumLow
Timedifferent
30-240 min20–45 min1-2 h60-90 min
Participantsdifferent
1-6Small cross-functional group4-124-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryRisk list, Mitigation plan, Assumption logAlignment Map, Open Issues, Decision QuestionsProblem Cluster, Prioritized Challenge, Experiment
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
RiskDecisionFailurePlanning
AlignmentStakeholdersStrategyFacilitation
FacilitationDecisionProblem solvingWorkshop
Add more methods