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 for Constraint Analysis.
Decision Making
Constraint Analysis
Paper illustration for Learning Review.
Operations
Learning Review
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Purposedifferent
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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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
LowMediumMedium
Timedifferent
30-90 min1-3 h30-90 min
Participantsdifferent
2-83-101-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Constraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesLearning Review Notes, System Factors, Improvement ActionsDecision Tree, Option Map, Assumption List
Tagsno overlap
ConstraintsDecisionPlanningOptions
LearningRetrospectiveIncidentOperations
DecisionTreeOptions
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for ALPEN Method
Operations
ALPEN Method
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem