View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Facilitation Stakeholder Mapping |  Facilitation Expectation Mapping |  Facilitation Storytelling |
|---|---|---|---|---|
Purposedifferent | 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. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | Half day initial, dann laufend | 60–90 min | 45-90 min | 45-120 min |
Participantsdifferent | Ein Team plus Stakeholder | 2-8 | 3-12 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Team API Document | Stakeholder Map, Engagement Plan, Risk Notes | Expectation Map, Alignment Notes, Agreements | Narrative Outline, Key Message, Story Arc |
Tagsno overlap | TeamAlignmentCommunicationService | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersTeam | CommunicationNarrativeStakeholdersFacilitation |