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 for Cynefin Workshop.
Decision Making
Cynefin Workshop
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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.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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
2-6 h60-180 min20–45 min1-3 h
Participantsdifferent
2-84-20Small cross-functional group1-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsCynefin Map, Domain-specific Actions, Sensemaking NotesRisk list, Mitigation plan, Assumption logArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
ComplexitySensemakingDecision
RiskDecisionFailurePlanning
SensemakingDecisionRationale
Add more methods