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 |  Product Strategy ICE Scoring |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
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 ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-2 Tage | 1-3 h | 30-60 min | 1-3 h |
Participantsdifferent | 10-50 | 2-8 | 2-8 | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Context Map, Integration Patterns, Boundary Notes | ICE Table, Top Idea List | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | SatisfactionPrioritizationCustomer | Domain-Driven DesignBoundariesStrategy | PrioritizationScoringGrowthDecision | Domain-Driven DesignBoundariesModeling |