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 | ![]() Decision Making Cynefin Workshop | ![]() Decision Making Argument Mapping |
|---|---|---|---|---|
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. | When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 15-45 min | 1 Tag bis mehrere Wochen | 60-180 min | 1-3 h |
Participantsdifferent | 1-3 | 4-10 | 4-20 | 1-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Problem Statement, Prototype, Test Learnings | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | InnovationPrototypeResearch | ComplexitySensemakingDecision | SensemakingDecisionRationale |



