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 of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Weekly Review.
Operations
Weekly Review
Purposedifferent
When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.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.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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
45-90 min1-2 h Setup, laufend1-3 h30-60 min
Participantsdifferent
3-812-81
Formatdifferent
WorkshopAsyncWorkshop + asyncAsync
Outputdifferent
Impact Map, Outcome Hypotheses, Delivery OptionsAction Lists, Project List, Review RoutineContext Map, Integration Patterns, Boundary NotesUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
OutcomesStrategyBehaviorPlanning
ProductivityPlanningTasksExecution
Domain-Driven DesignBoundariesStrategy
ProductivityExecutionPlanning
Add more methods