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
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Risk Storming.
Architecture
Risk Storming
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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitydifferent
HighLowMediumLow
Timedifferent
Mehrere Tage bis Wochen45-90 min2–4 h review as a planning range; preparation and evaluation additional60-90 min
Participantsdifferent
1-5 Modellierende, Stakeholder asynchron2-8Designers, developers as users, and facilitation4-12
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Simulation Model, Scenario ReportsAssumption List, Critical Assumptions, Learning PlanPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
Systems thinkingDynamicsSimulationAnalysis
AssumptionsRiskDecisionDiscovery
ArchitectureEngineeringFeedbackValidationTasks
RiskArchitectureWorkshopValidation
Add more methods