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 |  Business Strategy Three Horizons |  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. | Three Horizons helps clarify strategic options across different timeframes. It compares strengths, risks, market logic, and investment choices, and captures the result as a horizon map, portfolio view, and initiatives per horizon. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 1-3 h | Halbtags-Workshop, dann iterativ | 1-3 h |
Participantsdifferent | 10-50 | 2-8 | 3-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Context Map, Integration Patterns, Boundary Notes | Horizon map, Portfolio view, Initiatives per horizon, Resource plan | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | SatisfactionPrioritizationCustomer | Domain-Driven DesignBoundariesStrategy | StrategyInnovationPortfolioForesight | Domain-Driven DesignBoundariesModeling |