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
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Purposedifferent
Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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.
Complexitydifferent
LowMedium
Timedifferent
30 min Setup, dann laufend2-6 h
Participantsdifferent
1-3 maintaining, briefing for everyone2-8
Formatdifferent
AsyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourceEvent Model, UI Flow, Commands, Read Models
Tagsno overlap
RiskTrackingStakeholdersGovernance
EventsBlueprintDomain-Driven DesignBehavior
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 of Stakeholder Salience Model with its method-specific working model.
Facilitation
Stakeholder Salience Model