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 RecordSailboat RetrospectiveArchitecture Communication CanvasViews and Beyond
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Agile Sailboat Retrospective | ![]() Architecture Architecture Communication Canvas | ![]() 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Low | Medium | Medium |
Timedifferent | 15-45 min | 45-90 min | 60-120 min | 1-3 Tage |
Participantsdifferent | 1-3 | 4-12 | 2-8 | 1-4 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Sailboat Board, Risks, Improvement Actions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RetrospectiveTeamImprovement | ArchitectureCommunicationStakeholdersCanvas | DocumentationStakeholdersArchitecture |



