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
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 notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration for Eat the Frog
Operations
Eat the Frog
Paper illustration for Weekly Review.
Operations
Weekly Review
Purposedifferent
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.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.The method protects energy and attention for the task that creates the largest progress and is often postponed.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
MediumMediumLowLow
Timedifferent
2-8 h1-2 h Setup, laufend15-90 min daily30-60 min
Participantsdifferent
5-12111
Formatdifferent
WorkshopAsyncAsyncAsync
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsAction Lists, Project List, Review RoutinePriority Task, Completion Note, Daily FocusUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
ProductivityPlanningTasksExecution
PrioritizationProductivityFocusExecution
ProductivityExecutionPlanning
Add more methods