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 EventStorming |  Facilitation Decision Jam |
|---|---|---|---|
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 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 decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-2 Tage | 2-8 h | 60-90 min |
Participantsdifferent | 10-50 | 5-12 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | SatisfactionPrioritizationCustomer | Domain-Driven DesignEventsDiscoveryWorkshop | FacilitationDecisionProblem solvingWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
