View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Concept Mapping |  Domain Modeling EventStorming |  Decision Making Red Teaming |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-2 h | 2-8 h | 1-4 h | 45-90 min |
Participantsdifferent | 1-8 | 5-12 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Challenge Findings, Risk Register, Mitigation Plan | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Domain-Driven DesignEventsDiscoveryWorkshop | RiskDecisionSensemaking | AssumptionsRiskDecisionDiscovery |