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 Weekly Review.
Operations
Weekly Review
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
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
Purposedifferent
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 a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
30-60 min2-8 h45-90 min1-2 h Setup, laufend
Participantsdifferent
15-123-81
Formatdifferent
AsyncWorkshopWorkshopAsync
Outputdifferent
Updated Task System, Weekly Focus, Next ActionsEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsImpact Map, Outcome Hypotheses, Delivery OptionsAction Lists, Project List, Review Routine
Tagsno overlap
ProductivityExecutionPlanning
Domain-Driven DesignEventsDiscoveryWorkshop
OutcomesStrategyBehaviorPlanning
ProductivityPlanningTasksExecution
Add more methods