View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Three-Point Estimation | ![]() Architecture arc42 | ![]() Facilitation Dot Estimation | ![]() Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 10-30 min je Item | 1-2 Tage | 5-20 min | 1-4 h |
Participantsdifferent | 1-8 | 1-4 | 3-20 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Three-Point Estimate, Risk Range, Assumption Notes | Architecture Document, Context View, Runtime View, Deployment View | Effort Heatmap, Risk Signals, Discussion Targets | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | EstimationUncertaintyForecasting | ArchitectureDocumentationCommunication | EstimationEffortRisk | ArchitectureCommunicationVisualization |



