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 Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
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.In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most 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 strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.
Complexitydifferent
MediumMediumLowHigh
Timedifferent
2-4 h1-3 h20–45 min1-4 h
Participantsdifferent
4-103-8Small cross-functional group3-8
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Story Map, Release Slices, Backlog CandidatesFailure Scenarios, Risk Notes, Control Gaps, Test and Response ActionsRisk list, Mitigation plan, Assumption logChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
BacklogJourneyPlanningMVP
FailureResilienceRisk
RiskDecisionFailurePlanning
RiskDecisionSensemaking
Add more methods