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 Stakeholder Mapping |  Facilitation Storytelling |  Architecture Software Architecture Canvas |
|---|---|---|---|
Purposedifferent | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 60–90 min | 45-120 min | 1-2 h |
Participantsdifferent | 2-8 | 1-6 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Stakeholder Map, Engagement Plan, Risk Notes | Narrative Outline, Key Message, Story Arc | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | StakeholdersAlignmentFacilitationChange | CommunicationNarrativeStakeholdersFacilitation | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
