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 |  Product Discovery Hypothesis Prioritization Canvas |  Product Discovery Test Card |
|---|---|---|---|
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 many hypotheses compete for attention, it brings order to their learning sequence and importance. It separates problem, assumption, solution, and evidence. The result is captured as a prioritization canvas and a hypothesis backlog. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min | 20-35 min |
Participantsdifferent | 3-20 Reviewer | 3-8 | 1-5 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Prioritization Canvas, Hypothesis Backlog | Test Card with a pre-set threshold |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ExperimentsPrioritizationDiscoveryHypothesis | ExperimentsValidationDiscoveryHypothesis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
