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
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
Paper illustration for Current Reality Tree
Systems Thinking
Current Reality Tree
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
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.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.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.A Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations.
Complexitydifferent
MediumHighHighMedium
Timedifferent
2-8 h2-6 h2-6 h1-3 h
Participantsdifferent
5-123-103-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsCurrent Reality Tree, Core Problems, Intervention IdeasCausal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
CausalityIncidentRoot causeTimeline
Systems thinkingRoot causeConstraintsCausality
FeedbackSystems thinkingCausalityDynamics
Add more methods