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 |  Growth A/B Testing |  Agile 4Ls Retrospective |  Growth Growth Experiment |
|---|---|---|---|---|
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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | When growth ideas surface quickly, the temptation to build immediately instead of learning is high. A Growth Experiment frames an assumption so target group, lever, and measurement are clear before the first deployment. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-3 h | 1-4 Wochen | 45–75 min | 1-2 Wochen |
Participantsdifferent | 3-10 | 1-6 | Team members involved | 1-6 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Experiment results, Decision log, Learning summary | 4Ls Board, Learning Themes, Improvement Actions | Experiment card, Result summary, Next bet |
Tagsno overlap | ProcessOperationsImprovement | ExperimentsGrowthAnalyticsValidation | RetrospectiveLearningReflectionTeam | MarketingGrowthExperimentsLearning |