methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration for Storytelling
Facilitation
Storytelling
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Purposedifferent
When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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
MediumMediumLowLow
Timedifferent
1-2 h45-120 minHalf day initial, dann laufend60–90 min
Participantsdifferent
4-121-6Ein Team plus Stakeholder2-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Alignment Map, Open Issues, Decision QuestionsNarrative Outline, Key Message, Story ArcTeam API DocumentStakeholder Map, Engagement Plan, Risk Notes
Tagsno overlap
AlignmentStakeholdersStrategyFacilitation
CommunicationNarrativeStakeholdersFacilitation
TeamAlignmentCommunicationService
StakeholdersAlignmentFacilitationChange
Add more methods