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 Team Charter.
Facilitation
Team Charter
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration for Delegation Poker.
Facilitation
Delegation 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.When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day.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.When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice.
Complexitydifferent
LowMediumMediumLow
Timedifferent
Half day initial, dann laufend2-4 h45-90 min45-90 min
Participantsdifferent
Ein Team plus Stakeholder3-123-123-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Team API DocumentTeam Charter, Working Norms, Role NotesRAPID Role Map, Recommendation, Decision LogDelegation Board, Decision Boundaries, Role Agreements
Tagsno overlap
TeamAlignmentCommunicationService
TeamAlignmentCollaboration
DecisionRolesGovernance
AutonomyRolesTeam
Add more methods