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 RAPID
Decision Making
RAPID
Paper illustration for DACI
Decision Making
DACI
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.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.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.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
LowMediumLowLow
Timedifferent
Half day initial, dann laufend45-90 min30-60 min45-90 min
Participantsdifferent
Ein Team plus Stakeholder3-122-103-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Team API DocumentRAPID Role Map, Recommendation, Decision LogDACI Matrix, Decision Owner, Decision LogExpectation Map, Alignment Notes, Agreements
Tagsno overlap
TeamAlignmentCommunicationService
DecisionRolesGovernance
DecisionRolesGovernanceAlignment
AlignmentStakeholdersTeam
Add more methods