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
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Purposedifferent
When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.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.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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
MediumHighMediumMedium
Timedifferent
2-8 h1-4 h1-3 h60-180 min
Participantsdifferent
5-123-83-124-20
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsChallenge Findings, Risk Register, Mitigation PlanKnowledge Map, Critical Knowledge Areas, Transfer PlanCynefin Map, Domain-specific Actions, Sensemaking Notes
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
RiskDecisionSensemaking
KnowledgeMappingRisk
ComplexitySensemakingDecision
Add more methods