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 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
Paper illustration for DACI
Decision Making
DACI
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.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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitydifferent
LowMediumLowLow
Timedifferent
45-90 min90-180 minHalf day initial, dann laufend30-60 min
Participantsdifferent
3-124-12Ein Team plus Stakeholder2-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Expectation Map, Alignment Notes, AgreementsDecision Rights Matrix, AgreementTeam API DocumentDACI Matrix, Decision Owner, Decision Log
Tags1 shared
AlignmentStakeholdersTeam
DecisionGovernanceAlignmentResponsibility
TeamAlignmentCommunicationService
DecisionRolesGovernanceAlignment
Add more methods