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 |  Knowledge Modeling Knowledge Mapping |  Architecture Architecture Decision Record |  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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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. | 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 | Medium | Low | Low |
Timedifferent | 1-2 h | 1-3 h | 15-45 min | 45-90 min |
Participantsdifferent | 2-8 | 3-12 | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Product Canvas, Product Assumptions, Scope Notes | Knowledge Map, Critical Knowledge Areas, Transfer Plan | ADR File, Decision Log, Rationale | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | CanvasDiscoveryScope | KnowledgeMappingRisk | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskDecisionDiscovery |