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 Problem Framing Workshop |  Facilitation Decision Jam |
|---|---|---|---|---|
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 team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-2 h | 2-8 h | 60-120 min | 60-90 min |
Participantsdifferent | 1-8 | 5-12 | 4-10 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Domain-Driven DesignEventsDiscoveryWorkshop | FacilitationAlignmentDiscovery | FacilitationDecisionProblem solvingWorkshop |