View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordArchitecture Communication CanvasSailboat RetrospectiveViews and Beyond
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Architecture Architecture Communication Canvas | ![]() Agile Sailboat Retrospective | ![]() Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | 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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 60-120 min | 45-90 min | 1-3 Tage |
Participantsdifferent | 1-3 | 2-8 | 4-12 | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Sailboat Board, Risks, Improvement Actions | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas | RetrospectiveTeamImprovement | DocumentationStakeholdersArchitecture |



