View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Working Backwards |  Architecture Request for Comments |  Decision Making DACI |  Decision Making RAPID |
|---|---|---|---|---|
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. | 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 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 4-8 h, mehrere Iterationen | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min | 45-90 min |
Participantsdifferent | 2-6 | 3-20 Reviewer | 2-10 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Future Press Release, FAQ, Vision Statement | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | DACI Matrix, Decision Owner, Decision Log | RAPID Role Map, Recommendation, Decision Log |
Tagsno overlap | VisionNarrativeAlignment | ArchitectureDecisionAsyncGovernance | DecisionRolesGovernanceAlignment | DecisionRolesGovernance |