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
Paper illustration for Behavior Over Time Graph.
Systems Thinking
Behavior Over Time Graph
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 Behavior Over Time Graph shows how a metric or observation develops over time. The method makes trends, breaks, and recurring patterns visible that get lost in snapshots.
Complexitydifferent
HighMediumHighLow
Timedifferent
Mehrere Tage bis Wochen2–4 h review as a planning range; preparation and evaluation additional1 Tag bis mehrere Wochen20-45 min
Participantsdifferent
1-5 Modellierende, Stakeholder asynchronDesigners, developers as users, and facilitation4-101-10
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 LearningsBehavior Over Time Graph, Trend Hypotheses, Key Events
Tagsno overlap
Systems thinkingDynamicsSimulationAnalysis
ArchitectureEngineeringFeedbackValidationTasks
InnovationPrototypeResearch
Systems thinkingPatternsDynamics
Add more methods