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 Views and Beyond | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 1-4 h | 6 Wochen Cycle + 2 Wochen Cool-Down | 1-3 Tage | 15-45 min |
Participantsdifferent | 1-5 | 2-4 pro Pitch | 1-4 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureCommunicationVisualization | PlanningDeliveryAutonomy | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance |



