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 |  Team Design Team API |  Facilitation Stakeholder Mapping |
|---|---|---|---|
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. | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 45-120 min | Half day initial, dann laufend | 60–90 min |
Participantsdifferent | 1-6 | Ein Team plus Stakeholder | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Narrative Outline, Key Message, Story Arc | Team API Document | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | CommunicationNarrativeStakeholdersFacilitation | TeamAlignmentCommunicationService | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
