View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Timeline | ![]() Agile 4Ls Retrospective | ![]() Agile Start Stop Continue |
|---|---|---|---|
Purposedifferent | When a project, incident, or change process is only remembered in fragments, Timeline brings the sequence back into a readable form. It makes turning points, precursors, and after-effects recognizable over the course of time. | 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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitysame | Low | Low | Low |
Timedifferent | 30-90 min | 45–75 min | 30-60 min |
Participantsdifferent | 2-12 | Team members involved | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Timeline, Milestones, Insight Notes | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | TimelineFacilitationSequence | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






