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 | ![]() Facilitation Decision Jam | ![]() 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. | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | 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 | Low | Low |
Timedifferent | 1-2 h | 2-8 h | 60-90 min | 45-90 min |
Participantsdifferent | 1-8 | 5-12 | 4-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Problem Cluster, Prioritized Challenge, Experiment | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Domain-Driven DesignEventsDiscoveryWorkshop | FacilitationDecisionProblem solvingWorkshop | AssumptionsRiskDecisionDiscovery |



