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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
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 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 decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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
MediumLowMediumHigh
Timedifferent
2-4 h20–45 min30-90 min1-4 h
Participantsdifferent
4-10Small cross-functional group1-63-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Story Map, Release Slices, Backlog CandidatesRisk list, Mitigation plan, Assumption logDecision Tree, Option Map, Assumption ListChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
BacklogJourneyPlanningMVP
RiskDecisionFailurePlanning
DecisionTreeOptions
RiskDecisionSensemaking
Add more methods