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 Knowledge Mapping |  Domain Modeling EventStorming |  Decision Making Cynefin Workshop |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | 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 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 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. | 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 | Medium | Low |
Timedifferent | 1-3 h | 2-8 h | 60-180 min | 45-90 min |
Participantsdifferent | 3-12 | 5-12 | 4-20 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | KnowledgeMappingRisk | Domain-Driven DesignEventsDiscoveryWorkshop | ComplexitySensemakingDecision | AssumptionsRiskDecisionDiscovery |