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 | ![]() Operations Time Blocking | ![]() Architecture Architecture Communication Canvas | ![]() Delivery Communication Plan |
|---|---|---|---|---|
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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1-2 h | 15-30 min Planung, laufend | 60-120 min | 45-90 min |
Participantsdifferent | 2-8 | 1 | 2-8 | 2-6 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Blocked Calendar, Capacity View, Focus Plan | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | PlanningTime managementFocus | ArchitectureCommunicationStakeholdersCanvas | CommunicationStakeholdersDeliveryPlanning |



