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 | ![]() Systems Thinking Evaporating Cloud | ![]() Decision Making Assumption Surfacing | ![]() Architecture arc42 |
|---|---|---|---|---|
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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 1-4 h | 60-120 min | 45-90 min | 1-2 Tage |
Participantsdifferent | 1-5 | 2-8 | 2-8 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Assumption List, Critical Assumptions, Learning Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureCommunicationVisualization | Theory of ConstraintsAssumptionsSystems thinking | AssumptionsRiskDecisionDiscovery | ArchitectureDocumentationCommunication |



