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 Affinity Estimation.
Agile
Affinity Estimation
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Constraint Analysis.
Decision Making
Constraint 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.When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.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.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
MediumMediumLowLow
Timedifferent
2-4 h30-90 min20–45 min30-90 min
Participantsdifferent
4-103-12Small cross-functional group2-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Story Map, Release Slices, Backlog CandidatesAffinity Size Map, Grouped Estimates, Unclear ItemsRisk list, Mitigation plan, Assumption logConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
BacklogJourneyPlanningMVP
EstimationBacklogRelative sizing
RiskDecisionFailurePlanning
ConstraintsDecisionPlanningOptions
Add more methods