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 of a four-quadrant grid with tasks sorted by importance and urgency and translated into actions.
Decision Making
Eisenhower Matrix
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.It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped.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-30 min30-60 min
Participantsdifferent
5-1211-61
Formatdifferent
WorkshopAsyncWorkshop + asyncAsync
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsAction Lists, Project List, Review RoutineEisenhower Matrix, Action List, Delegation NotesUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
ProductivityPlanningTasksExecution
PrioritizationFocusTasks
ProductivityExecutionPlanning
Add more methods