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 |  Innovation Design Sprint |  Decision Making Argument Mapping |
|---|---|---|---|
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 the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. | 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 | Medium | High | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 4-5 Tage | 1-3 h |
Participantsdifferent | 3-20 Reviewer | 5-8 | 1-8 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Prototype, Test Findings, Decision Rationale | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Design sprintPrototypeValidationInnovation | SensemakingDecisionRationale |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
