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)
Paper illustration of Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption Test
Paper illustration of Experiment Canvas with a method-specific labelled workspace.
Product Discovery
Experiment Canvas
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.When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report.When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric.
Complexitydifferent
HighMediumMediumLow
Timedifferent
Mehrere Tage bis Wochen2–4 h review as a planning range; preparation and evaluation additional1-2 Wochen pro Iteration30-60 min
Participantsdifferent
1-5 Modellierende, Stakeholder asynchronDesigners, developers as users, and facilitation2-61-5
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Simulation Model, Scenario ReportsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsPrioritized Assumption List, Test Plan, Results ReportCompleted Experiment Canvas, Success Metric
Tagsno overlap
Systems thinkingDynamicsSimulationAnalysis
ArchitectureEngineeringFeedbackValidationTasks
ExperimentsValidationDiscoveryAssumptions
ExperimentsValidationDiscoveryHypothesis
Add more methods