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 Communication Plan
Delivery
Communication Plan
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights 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 many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.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
LowLowMediumLow
Timedifferent
45-90 min45-90 min90-180 minHalf day initial, dann laufend
Participantsdifferent
3-122-64-12Ein Team plus Stakeholder
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Expectation Map, Alignment Notes, AgreementsCommunication Plan, Channel Matrix, Message CadenceDecision Rights Matrix, AgreementTeam API Document
Tagsno overlap
AlignmentStakeholdersTeam
CommunicationStakeholdersDeliveryPlanning
DecisionGovernanceAlignmentResponsibility
TeamAlignmentCommunicationService
Add more methods