View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Storytelling |  Architecture Software Architecture Canvas |  Delivery Communication Plan |
|---|---|---|---|
Purposedifferent | When an insight needs to have an effect, storytelling translates dry facts into a comprehensible development. It combines context, tension, and consequence into a form that people remember and pass on more easily. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | Medium | Low | Low |
Timedifferent | 45-120 min | 1-2 h | 45-90 min |
Participantsdifferent | 1-6 | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Narrative Outline, Key Message, Story Arc | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | CommunicationNarrativeStakeholdersFacilitation | CanvasArchitectureAlignmentWorkshop | CommunicationStakeholdersDeliveryPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
