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 Event Modeling |  Agile Example Mapping |  Innovation Design Charrette |  Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 2-6 h | 30-60 min | Halber Tag bis mehrere Tage | 45-90 min |
Participantsdifferent | 2-8 | 3-7 | 10-50 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Example Map, Acceptance Criteria, Open Questions | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | Behavior-Driven DevelopmentRequirementsExamplesRefinement | BrainstormingWorkshopCollaborationIdeation | BrainstormingIdeationCreativityDivergenceWorkshop |