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 |  Architecture Architecture Communication Canvas |  Knowledge Modeling Feynman Technique |  Architecture arc42 |
|---|---|---|---|---|
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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 1-2 h | 60-120 min | 20-60 min | 1-2 Tage |
Participantsdifferent | 2-8 | 2-8 | 1 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Plain-language Explanation, Knowledge Gaps, Study Notes | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | ArchitectureCommunicationStakeholdersCanvas | LearningKnowledgeUnderstanding | ArchitectureDocumentationCommunication |