View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Architecture Architecture Decision Record | ![]() Delivery Communication Plan | ![]() Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | 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. | 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 many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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 | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 15-45 min | 45-90 min | 1-3 Tage |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-3 | 2-6 | 1-4 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | ADR File, Decision Log, Rationale | Communication Plan, Channel Matrix, Message Cadence | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureRationaleDocumentationGovernance | CommunicationStakeholdersDeliveryPlanning | DocumentationStakeholdersArchitecture |



