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 Communication Plan |  Agile Ideal Days |  Facilitation Dot Estimation |
|---|---|---|---|---|
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. | 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. | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-4 h | 45-90 min | 15-60 min | 5-20 min |
Participantsdifferent | 1-5 | 2-6 | 2-9 | 3-20 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Communication Plan, Channel Matrix, Message Cadence | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | ArchitectureCommunicationVisualization | CommunicationStakeholdersDeliveryPlanning | EstimationEffortAgile | EstimationEffortRisk |