View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Innovation Design Thinking |  Operations A3 Problem Solving |  Innovation Design Sprint |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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 | Low | High | Medium | High |
Timedifferent | 15-45 min | 1 Tag bis mehrere Wochen | 45-90 min | 4-5 Tage |
Participantsdifferent | 1-3 | 4-10 | 2-5 | 5-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Problem Statement, Prototype, Test Learnings | A3 Report, Action Plan, Root Cause Analysis | Prototype, Test Findings, Decision Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | InnovationPrototypeResearch | LeanProblem solvingCoachingOperations | Design sprintPrototypeValidationInnovation |