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 Weekly Review.
Operations
Weekly Review
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for ALPEN Method
Operations
ALPEN Method
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.In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
30-90 min30-60 min1-3 h10-20 min daily
Participantsdifferent
1-612-81
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
Decision Tree, Option Map, Assumption ListUpdated Task System, Weekly Focus, Next ActionsContext Map, Integration Patterns, Boundary NotesDaily Plan, Time Estimates, Review Notes
Tagsno overlap
DecisionTreeOptions
ProductivityExecutionPlanning
Domain-Driven DesignBoundariesStrategy
PlanningTime managementProductivityOperations
Add more methods