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 |  Agile Example Mapping |  Knowledge Modeling NeOn Methodology |
|---|---|---|---|
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 story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | The NeOn Methodology structures ontology work as a controlled process with reuse, scenarios, and reviews. It is useful when ontologies should not emerge ad hoc but modularly and reusably. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 1-2 Tage | 30-60 min | Mehrere Wochen bis Monate |
Participantsdifferent | 10-50 | 3-7 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Example Map, Acceptance Criteria, Open Questions | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | SatisfactionPrioritizationCustomer | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OntologyMethodologyReuseSemanticEngineering |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
