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 Request for Comments |  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 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-2 h | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min |
Participantsdifferent | 2-8 | 3-20 Reviewer | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Product Canvas, Product Assumptions, Scope Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | CanvasDiscoveryScope | ArchitectureDecisionAsyncGovernance | AssumptionsRiskDecisionDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
