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 notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
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 for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration for Weekly Review.
Operations
Weekly Review
Purposedifferent
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 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 domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.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
1-2 h Setup, laufend2-8 h1-3 h30-60 min
Participantsdifferent
15-123-101
Formatdifferent
AsyncWorkshopWorkshopAsync
Outputdifferent
Action Lists, Project List, Review RoutineEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsDomain Context Map, Boundary Notes, Ownership MapUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
ProductivityPlanningTasksExecution
Domain-Driven DesignEventsDiscoveryWorkshop
Domain-Driven DesignContextBoundaries
ProductivityExecutionPlanning
Add more methods