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 DACI
Decision Making
DACI
Paper illustration for Concierge MVP
Product Discovery
Concierge MVP
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.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 an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution.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
LowLowMediumLow
Timedifferent
Half day initial, dann laufend30-60 min1-4 Wochen45-90 min
Participantsdifferent
Ein Team plus Stakeholder2-103-10 Kunden3-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Team API DocumentDACI Matrix, Decision Owner, Decision LogConcierge Learnings, Service Blueprint, MVP RisksDelegation Board, Decision Boundaries, Role Agreements
Tagsno overlap
TeamAlignmentCommunicationService
DecisionRolesGovernanceAlignment
MVPValidationServiceDiscovery
AutonomyRolesTeam
Add more methods