methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for Flywheel.
Growth
Flywheel
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Purposedifferent
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.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.When many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses.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
LowMediumMediumLow
Timedifferent
45–75 min60-120 min1-3 h30-60 min
Participantsdifferent
Team members involved3-81-53-12
Formatdifferent
WorkshopWorkshopAsyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsFlywheel Map, Friction Points, Growth Levers, Experiment BacklogFunnel report, Drop-off analysis, Optimization hypothesesStart Stop Continue Board, Improvement Actions
Tagsno overlap
RetrospectiveLearningReflectionTeam
GrowthRetentionConversion
AnalyticsConversionGrowth
RetrospectiveImprovementTeamReflection
Add more methods