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 of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration for DACI
Decision Making
DACI
Paper illustration for RAPID
Decision Making
RAPID
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 a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.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.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.
Complexitydifferent
LowMediumLowMedium
Timedifferent
Half day initial, dann laufend1-3 h30-60 min45-90 min
Participantsdifferent
Ein Team plus Stakeholder5-302-103-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Team API DocumentConsensus Clusters, Theme Titles, Priority AreasDACI Matrix, Decision Owner, Decision LogRAPID Role Map, Recommendation, Decision Log
Tagsno overlap
TeamAlignmentCommunicationService
FacilitationConsensusWorkshopAlignment
DecisionRolesGovernanceAlignment
DecisionRolesGovernance
Add more methods