View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Working BackwardsArchitecture Decision RecordProduct Vision BoardSoftware Architecture Canvas
| Criterion |  Product Discovery Working Backwards |  Architecture Architecture Decision Record |  Product Strategy Product Vision Board |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 4-8 h, mehrere Iterationen | 15-45 min | 1-2 h | 1-2 h |
Participantsdifferent | 2-6 | 1-3 | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Future Press Release, FAQ, Vision Statement | ADR File, Decision Log, Rationale | Product Vision Board, Vision Statement, Assumptions and Validation Questions | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | VisionNarrativeAlignment | ArchitectureRationaleDocumentationGovernance | VisionCanvasStrategyAlignment | CanvasArchitectureAlignmentWorkshop |