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 |  Delivery RAID Log |  Architecture Views and Beyond |  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. | 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. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 1-3 Tage | 1-4 h |
Participantsdifferent | 2-6 | 1-3 maintaining, briefing for everyone | 1-4 | 1-5 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Communication Plan, Channel Matrix, Message Cadence | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | CommunicationStakeholdersDeliveryPlanning | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture | ArchitectureCommunicationVisualization |