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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
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.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.
Complexitydifferent
MediumHigh
Timedifferent
2-8 hHalber Tag
Participantsdifferent
5-125-20
Formatsame
WorkshopWorkshop
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsSimulation Notes, Gaps List, Updated Runbooks
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
ResilienceOperationsIncident
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration of Starbursting with its method-specific working model.
Innovation
Starbursting