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
Stock and Flow Diagram method illustration showing its working structure
Systems Thinking
Stock and Flow Diagram
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
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 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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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
HighHighMediumMedium
Timedifferent
Mehrere Tage bis Wochen2-6 h45-60 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-5 Modellierende, Stakeholder asynchron1-62-8Designers, developers as users, and facilitation
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Simulation Model, Scenario ReportsStock and Flow Model, Dynamics Notes, Simulation HypothesesAssumption map, Test backlog, Risk rankingPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
Systems thinkingDynamicsSimulationAnalysis
DynamicsSimulationFeedbackSystems thinking
AssumptionsRiskExperimentsValidation
ArchitectureEngineeringFeedbackValidationTasks
Add more methods