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 Strategy Product Canvas |  Product Discovery Kano Model |  Delivery MoSCoW |
|---|---|---|---|
Purposedifferent | When product goal and feature scope don't yet fit cleanly together, it creates a shared working picture. It connects need, core features, and assumptions into a solid starting point. | 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 release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-2 h | 1-2 Tage | 30-90 min |
Participantsdifferent | 2-8 | 10-50 | 3-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Product Canvas, Product Assumptions, Scope Notes | Kano Matrix, Feature Classes, Priority Themes | Prioritized Backlog, Release Scope, Tradeoff Notes |
Tagsno overlap | CanvasDiscoveryScope | SatisfactionPrioritizationCustomer | PrioritizationScopeDecision |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
