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
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Purposedifferent
When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.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.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
45–75 min20–45 min30-90 min30-90 min
Participantsdifferent
Team members involvedSmall cross-functional group2-81-6
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsRisk list, Mitigation plan, Assumption logConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesDecision Tree, Option Map, Assumption List
Tagsno overlap
RetrospectiveLearningReflectionTeam
RiskDecisionFailurePlanning
ConstraintsDecisionPlanningOptions
DecisionTreeOptions
Add more methods