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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Purposedifferent
Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound.
Complexitydifferent
MediumLow
Timedifferent
2-6 h30-60 min
Participantsdifferent
2-83-7
Formatdifferent
Workshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsExample Map, Acceptance Criteria, Open Questions
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Add more methods

Often compared together

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

Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Paper illustration of Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
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