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 Tree Analysis.
Operations
Fault Tree Analysis
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Purposedifferent
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.Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs.DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitydifferent
HighHighLowMedium
Timedifferent
2-6 hMehrere Wochen1-2 h2-4 h
Participantsdifferent
3-82-6 researchers plus sample2-82-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesDIBB document, Belief list, Bet list, Learning reportBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
RiskRoot causeSafety
OutcomesInnovationResearchQuantitative
StrategyDecisionAssumptionsHypothesis
Root causeSafetyIncident
Add more methods