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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.
Complexitydifferent
MediumLow
Timedifferent
2-6 h20-40 min initial, dann laufend
Participantsdifferent
2-83-15
Formatsame
Workshop + asyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsROAM Board, Owner List
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
RiskAgileTrackingAlignment
Add more methods

Often compared together

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

Paper illustration for Diary Study.
UX Research
Diary Study
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 3-Circle Venn Diagram
Facilitation
3-Circle Venn Diagram