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 of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Purposedifferent
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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.
Complexitydifferent
MediumHighLowHigh
Timedifferent
45-90 min2-6 h30-60 min2-6 h
Participantsdifferent
3-83-102-83-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Impact Map, Outcome Hypotheses, Delivery OptionsFMEA Table, Risk Priority, Mitigation ActionsFishbone Diagram, Cause Categories, Investigation BacklogFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
OutcomesStrategyBehaviorPlanning
RiskQualityOperationsRoot cause
Root causeQualityOperations
RiskRoot causeSafety
Add more methods