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 arc42 | ![]() Decision Making Cynefin Workshop | ![]() Architecture C4 Model | ![]() Decision Making Red Teaming |
|---|---|---|---|---|
Purposedifferent | 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 problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. | 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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 1-2 Tage | 60-180 min | 1-4 h | 1-4 h |
Participantsdifferent | 1-4 | 4-20 | 1-5 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Context Diagram, Container Diagram, Component Diagram | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | ArchitectureDocumentationCommunication | ComplexitySensemakingDecision | ArchitectureCommunicationVisualization | RiskDecisionSensemaking |



