View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Domain Storytelling |  Domain Modeling Domain Context Map |  Knowledge Modeling IBIS |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 1-2 h | 1-3 h | 1-3 h | 15-45 min |
Participantsdifferent | 2-8 | 3-10 | 2-8 | 1-3 |
Formatdifferent | Workshop | Workshop | Workshop + async | Async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Domain Context Map, Boundary Notes, Ownership Map | Issue Map, Positions, Argument Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | Domain-Driven DesignContextBoundaries | RationaleKnowledgeDecision | ArchitectureRationaleDocumentationGovernance |