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 illustration for Behavior Over Time Graph.
Systems Thinking
Behavior Over Time Graph
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
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.A Behavior Over Time Graph shows how a metric or observation develops over time. The method makes trends, breaks, and recurring patterns visible that get lost in snapshots.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
MediumLowMedium
Timedifferent
2-6 h20-45 min1-3 h
Participantsdifferent
2-81-102-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsBehavior Over Time Graph, Trend Hypotheses, Key EventsCausal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
Systems thinkingPatternsDynamics
FeedbackSystems thinkingCausalityDynamics
Add more methods

Often compared together

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

Stock and Flow Diagram method illustration showing its working structure
Systems Thinking
Stock and Flow Diagram
Paper illustration of System Archetypes with its method-specific working model.
Systems Thinking
System Archetypes
Paper illustration for Current Reality Tree
Systems Thinking
Current Reality Tree
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