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 Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
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 Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Purposedifferent
Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying 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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
2-6 h15-45 min1-3 h60-180 min
Participantsdifferent
2-81-31-84-20
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsADR File, Decision Log, RationaleArgument Map, Evidence Gaps, Decision RationaleCynefin Map, Domain-specific Actions, Sensemaking Notes
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
ArchitectureRationaleDocumentationGovernance
SensemakingDecisionRationale
ComplexitySensemakingDecision
Add more methods