View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture arc42 |  Architecture Architecture Decision Record |  Facilitation Team Charter |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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 | Low | Low | Medium | Medium |
Timedifferent | 1-2 Tage | 15-45 min | 2-4 h | 60-120 min |
Participantsdifferent | 1-4 | 1-3 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Team Charter, Working Norms, Role Notes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | TeamAlignmentCollaboration | ArchitectureCommunicationStakeholdersCanvas |