View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Domain StorytellingTime BlockingArchitecture Communication CanvasArchitecture Inception Canvas
| Criterion | ![]() Knowledge Modeling Domain Storytelling | ![]() Operations Time Blocking | ![]() Architecture Architecture Communication Canvas | ![]() Architecture Architecture Inception Canvas |
|---|---|---|---|---|
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. | With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure. | 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 Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1-2 h | 15-30 min Planung, laufend | 60-120 min | 1-2 h |
Participantsdifferent | 2-8 | 1 | 2-8 | 3-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Blocked Calendar, Capacity View, Focus Plan | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | PlanningTime managementFocus | ArchitectureCommunicationStakeholdersCanvas | AlignmentArchitectureCanvas |



