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
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
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
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.When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.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.
Complexitydifferent
HighHighMediumHigh
Timedifferent
Mehrere Tage bis Wochen4-5 Tage2–4 h review as a planning range; preparation and evaluation additional1 Tag bis mehrere Wochen
Participantsdifferent
1-5 Modellierende, Stakeholder asynchron5-8Designers, developers as users, and facilitation4-10
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Simulation Model, Scenario ReportsPrototype, Test Findings, Decision RationalePrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsProblem Statement, Prototype, Test Learnings
Tagsno overlap
Systems thinkingDynamicsSimulationAnalysis
Design sprintPrototypeValidationInnovation
ArchitectureEngineeringFeedbackValidationTasks
InnovationPrototypeResearch
Add more methods