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 Discovery Working Backwards |  Decision Making Decision Rights Mapping |  Architecture Request for Comments |  Product Strategy Product Vision Board |
|---|---|---|---|---|
Purposedifferent | When the target state and benefit need to be clear first, it thinks backward from the desired outcome into the product logic. It sharpens vision, objections, and value proposition before elaboration. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. | When a product needs a shared direction, it connects target audience, benefit, and business picture in a clear vision. It makes the envisioned future legible for the team. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 4-8 h, mehrere Iterationen | 90-180 min | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 h |
Participantsdifferent | 2-6 | 4-12 | 3-20 Reviewer | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Future Press Release, FAQ, Vision Statement | Decision Rights Matrix, Agreement | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Product Vision Board, Vision Statement, Assumptions and Validation Questions |
Tagsno overlap | VisionNarrativeAlignment | DecisionGovernanceAlignmentResponsibility | ArchitectureDecisionAsyncGovernance | VisionCanvasStrategyAlignment |