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 Communication Plan |  Architecture Architecture Decision Record |  Delivery RAID Log |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | 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. | 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 C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 15-45 min | 30 min Setup, dann laufend | 1-4 h |
Participantsdifferent | 2-6 | 1-3 | 1-3 maintaining, briefing for everyone | 1-5 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Communication Plan, Channel Matrix, Message Cadence | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | CommunicationStakeholdersDeliveryPlanning | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationVisualization |