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 |  Growth A/B Testing |
|---|---|---|---|
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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | High | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 4-5 Tage | 1-4 Wochen |
Participantsdifferent | 3-20 Reviewer | 5-8 | 1-6 |
Formatdifferent | Async | Workshop | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Prototype, Test Findings, Decision Rationale | Experiment results, Decision log, Learning summary |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Design sprintPrototypeValidationInnovation | ExperimentsGrowthAnalyticsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
