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 Domain Storytelling | ![]() Operations Gemba Walk | ![]() Knowledge Modeling Knowledge Mapping | ![]() Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
Purposedifferent | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 1-2 h | 30-120 min | 1-3 h | 1-2 h |
Participantsdifferent | 2-8 | 2-6 | 3-12 | 1-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Observation Notes, Improvement Ideas | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | LeanObservationProcessOperations | KnowledgeMappingRisk | KnowledgeConceptsMappingSensemaking |



