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 System Dynamics Simulation with its method-specific working model.
Systems Thinking
System Dynamics Simulation
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
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.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.When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.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
HighMediumHighMedium
Timedifferent
Mehrere Tage bis Wochen1-3 h4-5 Tage2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-5 Modellierende, Stakeholder asynchron2-85-8Designers, developers as users, and facilitation
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
Simulation Model, Scenario ReportsCausal Loop Diagram, Feedback Notes, Leverage PointsPrototype, Test Findings, Decision RationalePrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
Systems thinkingDynamicsSimulationAnalysis
FeedbackSystems thinkingCausalityDynamics
Design sprintPrototypeValidationInnovation
ArchitectureEngineeringFeedbackValidationTasks
Add more methods