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 HEART Framework |  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 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. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | 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 | 120 min initial, dann laufend | 1-3 h |
Participantsdifferent | 10-50 | 3-8 | 3-6 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Context Canvas, Glossary, Integration Notes | HEART-GSM Table, Dashboard | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | SatisfactionPrioritizationCustomer | Domain-Driven DesignBoundariesModeling | MetricsUX researchMeasurementSatisfaction | Domain-Driven DesignContextBoundaries |