View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Kano Model |  Domain Modeling Context Map |  Domain Modeling EventStorming |  Domain Modeling Domain Context Map |
|---|---|---|---|---|
Purposedifferent | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 1-3 h | 2-8 h | 1-3 h |
Participantsdifferent | 10-50 | 2-8 | 5-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Context Map, Integration Patterns, Boundary Notes | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | SatisfactionPrioritizationCustomer | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignEventsDiscoveryWorkshop | Domain-Driven DesignContextBoundaries |