methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Red Teaming method illustration showing its working structure
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.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 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.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
LowLowMediumHigh
Timedifferent
1-2 Tage1-4 h60-180 min1-4 h
Participantsdifferent
1-41-54-203-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewContext Diagram, Container Diagram, Component DiagramCynefin Map, Domain-specific Actions, Sensemaking NotesChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
ArchitectureDocumentationCommunication
ArchitectureCommunicationVisualization
ComplexitySensemakingDecision
RiskDecisionSensemaking
Add more methods