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 Pre-Mortem |  Architecture arc42 |  Decision Making Constraint Analysis |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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 | 20–45 min | 1-2 Tage | 30-90 min | 1-4 h |
Participantsdifferent | Small cross-functional group | 1-4 | 2-8 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Architecture Document, Context View, Runtime View, Deployment View | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | RiskDecisionFailurePlanning | ArchitectureDocumentationCommunication | ConstraintsDecisionPlanningOptions | ArchitectureCommunicationVisualization |