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 Bounded Context Canvas |  UX Research Contextual Inquiry |
|---|---|---|---|
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 business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 1-3 h | 1-3 Wochen |
Participantsdifferent | 10-50 | 3-8 | 4-12 Beobachtungen |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Context Canvas, Glossary, Integration Notes | Field Notes, Workflow Insights, Pain Points |
Tagsno overlap | SatisfactionPrioritizationCustomer | Domain-Driven DesignBoundariesModeling | UX researchObservationContext |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
