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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Current Reality Tree
Systems Thinking
Current Reality Tree
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
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.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.A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once.For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.
Complexitydifferent
MediumMediumHighHigh
Timedifferent
2-8 h2-6 h2-6 h2-6 h
Participantsdifferent
5-122-83-83-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsEvent Model, UI Flow, Commands, Read ModelsCurrent Reality Tree, Core Problems, Intervention IdeasEvent Timeline, Causal Factor Chart, Cause List, Corrective Actions
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
EventsBlueprintDomain-Driven DesignBehavior
Systems thinkingRoot causeConstraintsCausality
CausalityIncidentRoot causeTimeline
Add more methods