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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for ALPEN Method
Operations
ALPEN Method
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 team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Purposedifferent
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.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.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.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitydifferent
MediumLowLowLow
Timedifferent
30-90 min10-20 min daily45–75 min30-60 min
Participantsdifferent
1-61Team members involved3-12
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Decision Tree, Option Map, Assumption ListDaily Plan, Time Estimates, Review Notes4Ls Board, Learning Themes, Improvement ActionsStart Stop Continue Board, Improvement Actions
Tagsno overlap
DecisionTreeOptions
PlanningTime managementProductivityOperations
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementTeamReflection
Add more methods