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 Architecture Decision Record |  Delivery RAID Log |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | 1-2 h | 15-45 min | 30 min Setup, dann laufend | 60-120 min |
Participantsdifferent | 2-8 | 1-3 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Product Canvas, Product Assumptions, Scope Notes | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | CanvasDiscoveryScope | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas |