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 for Delegation Poker.
Facilitation
Delegation Poker
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Purposedifferent
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.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.
Complexitydifferent
LowMediumLowMedium
Timedifferent
45-90 min45-90 min15-45 min1-3 h
Participantsdifferent
3-103-121-31-8
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsRAPID Role Map, Recommendation, Decision LogADR File, Decision Log, RationaleArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
AutonomyRolesTeam
DecisionRolesGovernance
ArchitectureRationaleDocumentationGovernance
SensemakingDecisionRationale
Add more methods