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
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
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.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.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.
Complexitydifferent
MediumMediumHigh
Timedifferent
2-8 h1-3 h1-4 h
Participantsdifferent
5-123-123-8
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsKnowledge Map, Critical Knowledge Areas, Transfer PlanChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
KnowledgeMappingRisk
RiskDecisionSensemaking
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop