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
Anonymous individual judgments pass through feedback loops to form a distribution.
Decision Making
Delphi Method
Paper illustration for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Purposedifferent
When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together.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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.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
HighMediumLowLow
Timedifferent
1-4 Wochen30-240 min60–90 min60-90 min
Participantsdifferent
6-30 Experten1-62-84-10
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Expert Forecast, Consensus Range, Assumption NotesHypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryStakeholder Map, Engagement Plan, Risk NotesProblem Cluster, Prioritized Challenge, Experiment
Tagsno overlap
ForecastingExpertsDecisionStrategy
TroubleshootingProblem solvingDiagnosis
StakeholdersAlignmentFacilitationChange
FacilitationDecisionProblem solvingWorkshop
Add more methods