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
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
Paper illustration of System Dynamics Simulation with its method-specific working model.
Systems Thinking
System Dynamics Simulation
Paper illustration for Risk Storming.
Architecture
Risk Storming
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
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.System Dynamics Simulation makes assumptions about time, delay, and feedback testable through experiments. It draws relationships, patterns, and feedback loops. The result is captured as a simulation model and scenario reports.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.
Complexitydifferent
MediumHighLowMedium
Timedifferent
1-3 hMehrere Tage bis Wochen60-90 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
2-81-5 Modellierende, Stakeholder asynchron4-12Designers, developers as users, and facilitation
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Causal Loop Diagram, Feedback Notes, Leverage PointsSimulation Model, Scenario ReportsAnnotated Diagram, Prioritized Risk List, Action BacklogPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
FeedbackSystems thinkingCausalityDynamics
Systems thinkingDynamicsSimulationAnalysis
RiskArchitectureWorkshopValidation
ArchitectureEngineeringFeedbackValidationTasks
Add more methods