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
Paper illustration of a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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.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.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
MediumLowMediumLow
Timedifferent
1-2 h15-45 min60-180 min1-2 Tage
Participantsdifferent
3-121-34-201-4
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsADR File, Decision Log, RationaleCynefin Map, Domain-specific Actions, Sensemaking NotesArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
Systems thinkingTradeoffsLeadership
ArchitectureRationaleDocumentationGovernance
ComplexitySensemakingDecision
ArchitectureDocumentationCommunication
Add more methods