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
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
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.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.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.
Complexitysame
MediumMediumMedium
Timedifferent
30-180 min1-3 h45-90 min
Participantsdifferent
1-62-83-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault AreaGap Matrix, Action Plan, Risk NotesImpact Map, Outcome Hypotheses, Delivery Options
Tagsno overlap
TroubleshootingDiagnosisEngineering
StrategyAnalysisPlanning
OutcomesStrategyBehaviorPlanning
Add more methods

Often compared together

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

Paper illustration of Value Chain Analysis with its method-specific working model.
Business Strategy
Value Chain Analysis
Paper illustration of Business Model Stress Test with its method-specific working model.
Business Strategy
Business Model Stress Test
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