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 Opportunity Solution Tree | ![]() Product Discovery Opportunity Interview | ![]() Operations After-Action Review |
|---|---|---|---|---|
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. | When discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 1-2 h Setup, laufend | 30-60 min je Interview | 20-45 min |
Participantsdifferent | 3-10 | 2-6 | 5-12 Interviews | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Opportunity Solution Tree, Experiment Backlog, Learning Log | Interview Notes, Opportunity Themes, Customer Quotes | Lessons learned, Action items, Event summary |
Tagsno overlap | ProcessOperationsImprovement | DiscoveryOutcomesExperimentsOpportunity | DiscoveryInterviewsOpportunityCustomer | LearningOperationsImprovement |



