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 |  Agile 4Ls Retrospective |  Growth Growth Experiment |  Agile Start Stop Continue |
|---|---|---|---|---|
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 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. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | Ongoing | 45–75 min | 1-2 Wochen | 30-60 min |
Participantsdifferent | 1-20 | Team members involved | 1-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Visual Board, Status Indicators, Exception Cues | 4Ls Board, Learning Themes, Improvement Actions | Experiment card, Result summary, Next bet | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | SignalsOperationsVisual management | RetrospectiveLearningReflectionTeam | MarketingGrowthExperimentsLearning | RetrospectiveImprovementTeamReflection |