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 of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Paper illustration for Responsibility Poker.
Facilitation
Responsibility Poker
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 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 it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences.
Complexitydifferent
LowMediumMediumLow
Timedifferent
Half day initial, dann laufend45-90 min90-180 min45-90 min
Participantsdifferent
Ein Team plus Stakeholder3-124-123-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Team API DocumentRAPID Role Map, Recommendation, Decision LogDecision Rights Matrix, AgreementResponsibility Map, Role Agreements, Open Questions
Tagsno overlap
TeamAlignmentCommunicationService
DecisionRolesGovernance
DecisionGovernanceAlignmentResponsibility
RolesResponsibilityTeamFacilitation
Add more methods