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 |  Agile Sailboat Retrospective |  Product Discovery Smoke Test |  Growth A/B Testing |
|---|---|---|---|---|
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 a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 1-3 h | 45-90 min | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 3-10 | 4-12 | Nutzertraffic | 1-6 |
Formatdifferent | Workshop | Workshop | Async | Async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Sailboat Board, Risks, Improvement Actions | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary |
Tagsno overlap | ProcessOperationsImprovement | RetrospectiveTeamImprovement | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation |