View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Argument Mapping |  Knowledge Modeling Domain Storytelling |  Architecture Architecture Decision Record |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 1-2 h | 15-45 min | 1-2 h |
Participantsdifferent | 1-8 | 2-8 | 1-3 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Argument Map, Evidence Gaps, Decision Rationale | Domain Story, Glossary Notes, Process Narrative | ADR File, Decision Log, Rationale | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | SensemakingDecisionRationale | KnowledgeDomain-Driven DesignProcess | ArchitectureRationaleDocumentationGovernance | KnowledgeConceptsMappingSensemaking |