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
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
LowMediumMediumLow
Timedifferent
1-2 Tage1-2 h60-180 min15-45 min
Participantsdifferent
1-41-84-201-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewConcept Map, Relationship Labels, Knowledge GapsCynefin Map, Domain-specific Actions, Sensemaking NotesADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
KnowledgeConceptsMappingSensemaking
ComplexitySensemakingDecision
ArchitectureRationaleDocumentationGovernance
Add more methods