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 horizontal story map with an activity backbone, task cards below it and a cross-map release line.
Product Discovery
User Story Mapping
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Purposedifferent
When user goals and delivery scope could drift apart, it orders the journey from goal to slice. It makes visible where an MVP can genuinely be cut.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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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
MediumHighLowMedium
Timedifferent
2-4 h2-6 h20–45 min2-4 h
Participantsdifferent
4-103-8Small cross-functional group2-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Story Map, Release Slices, Backlog CandidatesFault Tree, Critical Paths, Cause Hypotheses, Control ActionsRisk list, Mitigation plan, Assumption logBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
BacklogJourneyPlanningMVP
RiskRoot causeSafety
RiskDecisionFailurePlanning
Root causeSafetyIncident
Add more methods