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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Design Thinking as a learning loop: an observation notebook, a focused problem statement, different idea sketches, a cardboard prototype and user-test notes. Feedback leads to new understanding.
Innovation
Design Thinking
Stock and Flow Diagram method illustration showing its working structure
Systems Thinking
Stock and Flow Diagram
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.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.For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.A Stock and Flow Diagram shows how stocks, inflows, and outflows shape a system over time. It is especially suited when growth, delays, or capacity limits determine the dynamics.
Complexitydifferent
HighMediumHighHigh
Timedifferent
Mehrere Tage bis Wochen2–4 h review as a planning range; preparation and evaluation additional1 Tag bis mehrere Wochen2-6 h
Participantsdifferent
1-5 Modellierende, Stakeholder asynchronDesigners, developers as users, and facilitation4-101-6
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Simulation Model, Scenario ReportsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsProblem Statement, Prototype, Test LearningsStock and Flow Model, Dynamics Notes, Simulation Hypotheses
Tagsno overlap
Systems thinkingDynamicsSimulationAnalysis
ArchitectureEngineeringFeedbackValidationTasks
InnovationPrototypeResearch
DynamicsSimulationFeedbackSystems thinking
Add more methods