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 |  Operations Process Mapping |  Operations After-Action Review |  Operations Gemba Walk |
|---|---|---|---|---|
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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-2 Tage | 1-3 h | 20-45 min | 30-120 min |
Participantsdifferent | 10-50 | 3-10 | 3-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Process Map, Handoff List, Improvement Backlog | Lessons learned, Action items, Event summary | Observation Notes, Improvement Ideas |
Tagsno overlap | SatisfactionPrioritizationCustomer | ProcessOperationsImprovement | LearningOperationsImprovement | LeanObservationProcessOperations |