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 of Team API with its method-specific working model.
Team Design
Team API
Paper illustration for 3-Circle Venn Diagram
Facilitation
3-Circle Venn Diagram
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Stakeholder Mapping
Facilitation
Stakeholder Mapping
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 three perspectives matter at the same time, a Three-Circle Venn Diagram shows the overlaps and remainders precisely. It makes visible where shared effect arises and where only a partial perspective applies.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 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.
Complexitysame
LowLowLowLow
Timedifferent
Half day initial, dann laufend15-45 min45-90 min60–90 min
Participantsdifferent
Ein Team plus Stakeholder2-83-122-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Team API DocumentVenn Diagram, Overlap Notes, DifferentiatorsExpectation Map, Alignment Notes, AgreementsStakeholder Map, Engagement Plan, Risk Notes
Tags1 shared
TeamAlignmentCommunicationService
ComparisonFacilitationAlignment
AlignmentStakeholdersTeam
StakeholdersAlignmentFacilitationChange
Add more methods