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 |  Decision Making Assumption Surfacing |  Product Discovery Test Card |  Product Discovery Assumption 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 20-35 min | 45-60 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | 1-5 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Assumption List, Critical Assumptions, Learning Plan | Test Card with a pre-set threshold | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | AssumptionsRiskDecisionDiscovery | ExperimentsValidationDiscoveryHypothesis | AssumptionsRiskExperimentsValidation |