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 |  Architecture Architecture Decision Record |  Product Strategy Product Vision Board |  Architecture arc42 |
|---|---|---|---|---|
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. | 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 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 4-8 h, mehrere Iterationen | 15-45 min | 1-2 h | 1-2 Tage |
Participantsdifferent | 2-6 | 1-3 | 2-8 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Future Press Release, FAQ, Vision Statement | ADR File, Decision Log, Rationale | Product Vision Board, Vision Statement, Assumptions and Validation Questions | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | VisionNarrativeAlignment | ArchitectureRationaleDocumentationGovernance | VisionCanvasStrategyAlignment | ArchitectureDocumentationCommunication |