View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Kaizen Event |  Knowledge Modeling Event Modeling |  Product Discovery Opportunity Interview |  Domain Modeling EventStorming |
|---|---|---|---|---|
Purposedifferent | For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments. | 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 opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 0.5-5 Tage | 2-6 h | 30-60 min je Interview | 2-8 h |
Participantsdifferent | 4-10 | 2-8 | 5-12 Interviews | 5-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Kaizen Charter, Waste List, Improvement Experiments, Standard Work Update | Event Model, UI Flow, Commands, Read Models | Interview Notes, Opportunity Themes, Customer Quotes | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | LeanContinuous improvementOperations | EventsBlueprintDomain-Driven DesignBehavior | DiscoveryInterviewsOpportunityCustomer | Domain-Driven DesignEventsDiscoveryWorkshop |