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 C4 Model |  Delivery Shape Up |  Architecture Request for Comments |  Delivery Communication Plan |
|---|---|---|---|---|
Purposedifferent | 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. | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 1-4 h | 6 Wochen Cycle + 2 Wochen Cool-Down | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min |
Participantsdifferent | 1-5 | 2-4 pro Pitch | 3-20 Reviewer | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | ArchitectureCommunicationVisualization | PlanningDeliveryAutonomy | ArchitectureDecisionAsyncGovernance | CommunicationStakeholdersDeliveryPlanning |