View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Design Thinking | ![]() Architecture Architecture Decision Record | ![]() Operations A3 Problem Solving | ![]() 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. | 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 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 | High | Low | Medium | High |
Timedifferent | 1 Tag bis mehrere Wochen | 15-45 min | 45-90 min | 4-5 Tage |
Participantsdifferent | 4-10 | 1-3 | 2-5 | 5-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Problem Statement, Prototype, Test Learnings | ADR File, Decision Log, Rationale | A3 Report, Action Plan, Root Cause Analysis | Prototype, Test Findings, Decision Rationale |
Tagsno overlap | InnovationPrototypeResearch | ArchitectureRationaleDocumentationGovernance | LeanProblem solvingCoachingOperations | Design sprintPrototypeValidationInnovation |



