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 a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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 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.
Complexitysame
MediumMediumMedium
Timedifferent
1-2 h2-6 h1-3 h
Participantsdifferent
3-122-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsEvent Model, UI Flow, Commands, Read ModelsCausal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap
Systems thinkingTradeoffsLeadership
EventsBlueprintDomain-Driven DesignBehavior
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 for Behavior Over Time Graph.
Systems Thinking
Behavior Over Time Graph
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