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 Working Backwards with its method-specific working model.
Product Discovery
Working Backwards
Paper illustration for DACI
Decision Making
DACI
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
When the target state and benefit need to be clear first, it thinks backward from the desired outcome into the product logic. It sharpens vision, objections, and value proposition before elaboration.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.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 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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
4-8 h, mehrere Iterationen30-60 min45-90 min1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
2-62-103-123-20 Reviewer
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Future Press Release, FAQ, Vision StatementDACI Matrix, Decision Owner, Decision LogRAPID Role Map, Recommendation, Decision LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
VisionNarrativeAlignment
DecisionRolesGovernanceAlignment
DecisionRolesGovernance
ArchitectureDecisionAsyncGovernance
Add more methods