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 |  Product Strategy Lean Canvas |  Operations Gemba Walk |  Knowledge Modeling Domain Storytelling |
|---|---|---|---|---|
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 an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-2 h | 45-90 min | 30-120 min | 1-2 h |
Participantsdifferent | 1-8 | 1-6 | 2-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Lean Canvas, Core Assumptions, Experiment Backlog | Observation Notes, Improvement Ideas | Domain Story, Glossary Notes, Process Narrative |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | StartupLeanAssumptionsBusiness model | LeanObservationProcessOperations | KnowledgeDomain-Driven DesignProcess |