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 Architecture Decision Record |  Product Strategy Impact Mapping |  Product Discovery Test Card |  Product Discovery Hypothesis Prioritization Canvas |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 45-90 min | 20-35 min | 60-90 min |
Participantsdifferent | 1-3 | 3-8 | 1-5 | 3-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Impact Map, Outcome Hypotheses, Delivery Options | Test Card with a pre-set threshold | Prioritization Canvas, Hypothesis Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | OutcomesStrategyBehaviorPlanning | ExperimentsValidationDiscoveryHypothesis | ExperimentsPrioritizationDiscoveryHypothesis |