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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
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.For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.
Complexitydifferent
MediumLow
Timedifferent
2-6 h20-60 min
Participantsdifferent
2-81-4
Formatdifferent
Workshop + asyncAsync
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsRunbook, Checklist, Escalation Path
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
OperationsReliabilityDocumentation
Add more methods

Often compared together

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

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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
A paper-based illustration representing Service Blueprint with its core stages and visible working result.
UX Design
Service Blueprinting
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving