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 arc42 |  Facilitation Dot Estimation |  Architecture C4 Model |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. | 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 | 30 min Setup, dann laufend | 1-2 Tage | 5-20 min | 1-4 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-4 | 3-20 | 1-5 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View | Effort Heatmap, Risk Signals, Discussion Targets | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication | EstimationEffortRisk | ArchitectureCommunicationVisualization |