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 8D Problem Solving.
Operations
8D Problem Solving
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.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.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
MediumMediumHighLow
Timedifferent
2-8 h1-2 h Setup, laufend1-6 Wochen30-60 min
Participantsdifferent
5-1214-101
Formatdifferent
WorkshopAsyncWorkshop + asyncAsync
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsAction Lists, Project List, Review Routine8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
ProductivityPlanningTasksExecution
QualityProblem solvingRoot cause
ProductivityExecutionPlanning
Add more methods