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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of System Dynamics Simulation with its method-specific working model.
Systems Thinking
System Dynamics Simulation
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Stock and Flow Diagram method illustration showing its working structure
Systems Thinking
Stock and Flow Diagram
Purposedifferent
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.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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.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
MediumHighMediumHigh
Timedifferent
2–4 h review as a planning range; preparation and evaluation additionalMehrere Tage bis Wochen1-4 h2-6 h
Participantsdifferent
Designers, developers as users, and facilitation1-5 Modellierende, Stakeholder asynchron3-81-6
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsSimulation Model, Scenario ReportsProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanStock and Flow Model, Dynamics Notes, Simulation Hypotheses
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
Systems thinkingDynamicsSimulationAnalysis
Root causeProblem solvingQualityIncident
DynamicsSimulationFeedbackSystems thinking
Add more methods