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 Visual Management |  Growth A/B Testing |  Agile Starfish Retrospective |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work. | 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | 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. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | Ongoing | 1-4 Wochen | 45-90 min | 45-90 min |
Participantsdifferent | 1-20 | 1-6 | 4-12 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Visual Board, Status Indicators, Exception Cues | Experiment results, Decision log, Learning summary | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | SignalsOperationsVisual management | ExperimentsGrowthAnalyticsValidation | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement |