Purpose
The method helps clarify backlog, sprint work, and team flow concretely. It helps sort work by value, risk, and deliverability. The result is captured as a 4Ls Board, Learning Themes, and Improvement Actions.
Agile
4Ls Retrospective
Turns backlog, sprint work, and team flow into a tangible result by setting the timeframe, collecting liked and learned items, and selecting actions.
What worked well, what did the team learn, what was missing, and what does the team want for the future?
LowWorkshop45-75 min
How it works
The team follows the steps: clarify the timeframe, collect liked and learned, collect lacked and longed-for, cluster them, and select actions. Each step is captured visibly. In the end, a 4Ls Board, Learning Themes, and Improvement Actions are available so decisions, tests, or actions can follow directly.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Clarify the timeframe
- 2Collect liked and learned
- 3Collect lacked and longed-for
- 4Cluster them
- 5Select actions
The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- Sprint Retrospectives
- Project Closure
- Learning Reviews
Not good for
- Acute incident analysis
- Decision workshops without reflection
Deep dive
In detail
4Ls Retrospective follows a clear working logic: clarify the timeframe, collect liked and learned, collect lacked and longed-for, cluster items, and select actions. This turns the method into a visible thinking process instead of only a conversation. The participants move step by step from raw material, observations, or options to a shared structure. As a result, a 4Ls Board, Learning Themes, and Improvement Actions support decisions, learning, or further planning.
Facilitation
Prepare a clear guiding question, the right information, and a visible workspace. Plan about 45 to 75 minutes with 3 to 12 people and use the format in a facilitated workshop. Keep facilitation lightweight; short timeboxes, visible intermediate results, and a parking lot for open questions are helpful.
Output artifacts
4Ls BoardLearning ThemesImprovement Actions
Artifact templates
4Ls Retrospective Working TemplateCompact working template for the 4Ls retrospective with liked, learned, lacked, and longed for items.canvas
4Ls Retrospective Working TemplateCompact working template for the 4Ls retrospective with liked, learned, lacked, and longed for items.
canvas4ls-retrospective-working-template.md
Compact working template for the 4Ls retrospective with liked, learned, lacked, and longed for items.
4Ls Retrospective Working Template
Goal
Capture what the team liked, learned, lacked, and longed for in a structured review.
Context
Which time frame or event should the team review?
Input
- Time frame:
- Team or group:
- Notes, signals, or examples:
Working area
- Liked:
- Learned:
- Lacked:
- Longed for:
- Patterns:
Output artifacts
- 4Ls board:
- Learning themes:
- Improvement actions:
Open questions
- ...
Decision / next step
Owner, date, and success signal.
When to choose differently
Short decision aid for existing alternatives.
Start Stop Continue
Statt 4Ls Retrospective, wenn ihr Teamarbeit, Backlog oder Retrospektiven in einem leichten Arbeitsformat organisieren wollt.
Similar methods
All methodsAgile
Starfish Retrospective
Turns backlog, sprint work, and team flow into a tangible result by explaining five categories, collecting inputs, and formulating experiments.
Agile
Start Stop Continue
Turns backlog, sprint work, and team flow into a tangible result by setting context and timeframe, collecting start ideas, and prioritizing actions.
Statt 4Ls Retrospective, wenn ihr Teamarbeit, Backlog oder Retrospektiven in einem leichten Arbeitsformat organisieren wollt.
Agile
Mad Sad Glad
Turns backlog, sprint work, and team flow into a tangible result by defining the timeframe, collecting signals of mad, sad, and glad, and deriving patterns and actions.
Agile
Sailboat Retrospective
Turns backlog, sprint work, and team flow into a tangible result by defining the destination island, collecting drivers and anchors, and agreeing on actions.
Agile
Working Agreements
Turns team flow, expectations, and delivery rhythm into a tangible result by clarifying work context, collecting expectations, and setting a review cadence.
Agile
Sprint Retrospective
Turns sprint backlog, sprint execution, and team flow into a tangible result through reflecting on the sprint, collecting positives and challenges, and carrying actions into the next sprint.