View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Product CanvasAssumption SurfacingArchitecture Decision RecordArchitecture Communication Canvas
| Criterion | ![]() Product Strategy Product Canvas | ![]() Decision Making Assumption Surfacing | ![]() Architecture Architecture Decision Record | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-2 h | 45-90 min | 15-45 min | 60-120 min |
Participantsdifferent | 2-8 | 2-8 | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Product Canvas, Product Assumptions, Scope Notes | Assumption List, Critical Assumptions, Learning Plan | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | CanvasDiscoveryScope | AssumptionsRiskDecisionDiscovery | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas |



