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 |  Innovation Lotus Blossom |  Innovation Brainstorming |
|---|---|---|---|---|
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 central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-2 h | 2-8 h | 45-90 min | 30-60 min |
Participantsdifferent | 1-8 | 5-12 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Lotus Diagram, Idea Themes, Shortlist | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Domain-Driven DesignEventsDiscoveryWorkshop | BrainstormingIdeationCreativityDivergenceWorkshop | BrainstormingIdeationCreativityWorkshopDivergence |