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 ALPEN Method
Operations
ALPEN Method
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
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
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.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.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
LowMediumLowLow
Timedifferent
10-20 min daily30-90 min45–75 min30-60 min
Participantsdifferent
11-6Team members involved3-12
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Daily Plan, Time Estimates, Review NotesDecision Tree, Option Map, Assumption List4Ls Board, Learning Themes, Improvement ActionsStart Stop Continue Board, Improvement Actions
Tagsno overlap
PlanningTime managementProductivityOperations
DecisionTreeOptions
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementTeamReflection
Add more methods