View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Strategy Product Canvas |  Architecture Architecture Decision Record |  Product Discovery Assumption Mapping |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | When product goal and feature scope don't yet fit cleanly together, it creates a shared working picture. It connects need, core features, and assumptions into a solid starting point. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-2 h | 15-45 min | 45-60 min | 45-90 min |
Participantsdifferent | 2-8 | 1-3 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Product Canvas, Product Assumptions, Scope Notes | ADR File, Decision Log, Rationale | Assumption map, Test backlog, Risk ranking | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | CanvasDiscoveryScope | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskExperimentsValidation | AssumptionsRiskDecisionDiscovery |