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 illustration for Learning Review.
Operations
Learning 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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitysame
MediumMedium
Timedifferent
2-8 h1-3 h
Participantsdifferent
5-123-10
Formatsame
WorkshopWorkshop
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
LearningRetrospectiveIncidentOperations
Add more methods

Often compared together

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

A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling