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 RecordSoftware Architecture CanvasArchitecture Communication Canvas
| Criterion |  Product Discovery Working Backwards |  Architecture Architecture Decision Record |  Architecture Software Architecture Canvas |  Architecture Architecture Communication 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 4-8 h, mehrere Iterationen | 15-45 min | 1-2 h | 60-120 min |
Participantsdifferent | 2-6 | 1-3 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Future Press Release, FAQ, Vision Statement | ADR File, Decision Log, Rationale | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | VisionNarrativeAlignment | ArchitectureRationaleDocumentationGovernance | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas |