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 Argument Mapping
Decision Making
Argument Mapping
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for RAPID
Decision Making
RAPID
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.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.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.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
LowMediumMediumMedium
Timedifferent
45-90 min1-3 h1-3 Wochen vom Draft bis zur Entscheidung45-90 min
Participantsdifferent
3-101-83-20 Reviewer3-12
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsArgument Map, Evidence Gaps, Decision RationaleRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsRAPID Role Map, Recommendation, Decision Log
Tagsno overlap
AutonomyRolesTeam
SensemakingDecisionRationale
ArchitectureDecisionAsyncGovernance
DecisionRolesGovernance
Add more methods