View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Process Mapping | ![]() Product Discovery Outcome-Driven Innovation | ![]() Operations After-Action Review | ![]() Operations Gemba Walk |
|---|---|---|---|---|
Purposedifferent | 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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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 | High | Low | Low |
Timedifferent | 1-3 h | Mehrere Wochen | 20-45 min | 30-120 min |
Participantsdifferent | 3-10 | 2-6 researchers plus sample | 3-12 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Lessons learned, Action items, Event summary | Observation Notes, Improvement Ideas |
Tagsno overlap | ProcessOperationsImprovement | OutcomesInnovationResearchQuantitative | LearningOperationsImprovement | LeanObservationProcessOperations |



