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 C4 Model | ![]() Agile Ideal Days |
|---|---|---|---|
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. | 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 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 10-30 min je Item | 1-4 h | 15-60 min |
Participantsdifferent | 1-8 | 1-5 | 2-9 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Three-Point Estimate, Risk Range, Assumption Notes | Context Diagram, Container Diagram, Component Diagram | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | EstimationUncertaintyForecasting | ArchitectureCommunicationVisualization | EstimationEffortAgile |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






