4Ls retrospective template
Liked, Learned, Lacked, Longed for. A broader look at the sprint that leaves room for learning and unmet needs.
The columns and what to ask
Liked
What did you enjoy or appreciate?
Learned
What did you learn about the product, the process or each other?
Lacked
What was missing that would have helped?
Longed For
What do you wish you had, or wish we could do?
Best for
- The end of a project, release or quarter
- Teams that want to capture learning, not only problems
- Moments when Good / Bad / Improve feels repetitive
Skip it when
- You only have 30 minutes. Four columns need more time to read and cluster.
- The team needs quick, concrete process changes. Start / Stop / Continue gets there faster.
How to run it in 60 minutes
Sized for a team of up to eight. Add time for larger groups.
- 1
Set the stage · 5 min
Explain the four columns. Point out that Learned is as valuable as anything that went wrong.
- 2
Write cards · 10 min
Everyone fills all four columns silently. It's fine if a card could sit in two of them.
- 3
Read and cluster · 10 min
Group cards by theme rather than by column. Themes that cross columns often show the real story.
- 4
Discuss · 25 min
Vote for the themes to discuss. Give Lacked and Longed For the most time, since that is where changes come from.
- 5
Commit to actions · 10 min
Pick one thing to fix from Lacked and one to try from Longed For, with owners.
Facilitation tips
- Lacked is what was missing (tools, information, time). Longed For is aspirational. If people mix them up, cluster by theme instead.
- The Learned column is good raw material for a team wiki, a demo or onboarding notes.
- Longed For cards are often ideas for experiments. Choose one to actually try.
- Allow a bit longer than a three-column retro. Four columns produce more to read.
Questions
- What do the 4Ls stand for?
- Liked, Learned, Lacked and Longed for. Two columns look back at what happened (Liked, Learned) and two look at gaps and wishes (Lacked, Longed For).
- When is 4Ls better than Good / Bad / Improve?
- When you want to capture learning and unmet needs as well as problems, most often at the end of a project or after a release.
Run it with your team now
Your board opens with these columns. Votes, timers and anonymous cards are built in.
Start a 4Ls retroOther retrospective formats
- Mad / Sad / GladA retrospective that names feelings, not just facts. Useful when morale, not process, is the real issue.
- SailboatA visual metaphor: what pushes you forward, what holds you back, and what risks lie ahead.
- Good / Bad / ImproveThe simplest retrospective format: what went well, what didn't, and what to change next sprint.