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 Fault Isolation.
Engineering
Fault Isolation
Scenario Planning method illustration showing its working structure
Business Strategy
Scenario Planning
Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Purposedifferent
In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected.Scenario Planning opens the view to several plausible futures instead of a single forecast. The method protects strategies from depending on too narrow an expected path.When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.
Complexitydifferent
MediumHighMedium
Timedifferent
30-180 min0.5-2 Tage45-90 min
Participantsdifferent
1-64-123-8
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault AreaScenario Set, Strategic Implications, Robust OptionsImpact Map, Outcome Hypotheses, Delivery Options
Tagsno overlap
TroubleshootingDiagnosisEngineering
StrategyUncertaintyPlanning
OutcomesStrategyBehaviorPlanning
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Business Model Stress Test with its method-specific working model.
Business Strategy
Business Model Stress Test
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Paper illustration of GIST Planning with its method-specific working model.
Product Strategy
GIST Planning
Paper illustration for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting