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 Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for Storytelling
Facilitation
Storytelling
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
Purposedifferent
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.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 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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
45-90 min45-120 min1-2 hHalf day initial, dann laufend
Participantsdifferent
3-121-64-12Ein Team plus Stakeholder
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Expectation Map, Alignment Notes, AgreementsNarrative Outline, Key Message, Story ArcAlignment Map, Open Issues, Decision QuestionsTeam API Document
Tagsno overlap
AlignmentStakeholdersTeam
CommunicationNarrativeStakeholdersFacilitation
AlignmentStakeholdersStrategyFacilitation
TeamAlignmentCommunicationService
Add more methods