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 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
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
Purposedifferent
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 Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations.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 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.
Complexitydifferent
HighMediumMediumHigh
Timedifferent
1 Tag bis mehrere Wochen1-3 h2–4 h review as a planning range; preparation and evaluation additional4-5 Tage
Participantsdifferent
4-102-8Designers, developers as users, and facilitation5-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Problem Statement, Prototype, Test LearningsCausal Loop Diagram, Feedback Notes, Leverage PointsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsPrototype, Test Findings, Decision Rationale
Tagsno overlap
InnovationPrototypeResearch
FeedbackSystems thinkingCausalityDynamics
ArchitectureEngineeringFeedbackValidationTasks
Design sprintPrototypeValidationInnovation
Add more methods