View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Agile Starfish Retrospective |  Decision Making RAPID |
|---|---|---|---|
Purposedifferent | 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. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | 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 | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 45-90 min |
Participantsdifferent | 3-20 Reviewer | 4-12 | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Starfish Board, Practice Changes, Experiments | RAPID Role Map, Recommendation, Decision Log |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RetrospectiveImprovementExperimentsTeam | DecisionRolesGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
