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 objective sheet with five SMART fields, baseline, target, owner, deadline and a complete result statement.
Product Strategy
SMART Goals
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation 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 goals are formulated too generally, it brings measurability, direction, and timing into shape. It prevents intentions from staying without clear verification.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 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.
Complexitydifferent
LowLowMediumLow
Timedifferent
Half day initial, dann laufend15-30 min1-2 h45-90 min
Participantsdifferent
Ein Team plus Stakeholder1-84-123-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Team API DocumentSMART Goal, Measurement Note, DeadlineAlignment Map, Open Issues, Decision QuestionsExpectation Map, Alignment Notes, Agreements
Tags1 shared
TeamAlignmentCommunicationService
GoalsPlanningMeasurementAlignment
AlignmentStakeholdersStrategyFacilitation
AlignmentStakeholdersTeam
Add more methods