Framework · Facilitation techniques · 3 min read
4Ls retro
Liked / Learned / Lacked / Longed for: a learning-focused retrospective that helps a team reflect on what it learned and pick 1–2 experiments.
What went well and what you enjoyed. Keep doing it.
e.g. "Pairing with developers on day one"New knowledge, skills or insights, about the work or the team.
e.g. "Users print the report weekly"What was missing or got in the way.
e.g. "Access to real production data"What you wish you had had. Often the seed of an experiment.
e.g. "A fixed weekly review slot"Silent writing per L → cluster → discuss → pick 1–2 experiments
Use it when
- A project or quarter has ended and you want the team to reflect on learning, not only on problems.
- Your team is tired of the classic "went well / didn't go well" retro and needs a fresh format.
- A team has just tried something new, for example a new research method or a design-system pilot, and you want to capture what it taught you.
How to use it
- Set the scope and the goal. Name the period or project you are looking back on, and say that the session ends with 1–2 experiments. Prepare four columns on a board. Output: a board with Liked, Learned, Lacked, Longed for. 5 minutes.
- Write silently, one L at a time. Give a few minutes per column. One thought per sticky, no talking. Output: stickies in all four columns. About 10 minutes.
- Read and cluster. Each person reads their stickies briefly. Then group similar stickies within each column. Output: clusters per L. About 10 minutes.
- Discuss the patterns. Start with Liked and Learned, then Lacked and Longed for. Ask "What does this tell us?" and link Lacked items to Longed-for items. Output: 3–4 themes the team agrees on. About 15 minutes.
- Pick 1–2 experiments. Turn the strongest themes into small experiments with an owner and a date. Use Dot voting if there are many candidates. Output: 1–2 experiments in the retro notes. About 5 minutes.
Worked example
A UX lead runs a 45-minute 4Ls retro with 6 designers after a quarter of work on a shared design system for an internal operations platform.
| L | Main cluster | What the team said |
|---|---|---|
| Liked | Cross-team critique | "Seeing other teams' work saved us from building the same thing twice." |
| Learned | Users and data tables | "Planners filter by date first. We had assumed they filter by status." |
| Lacked | Developer time | "Components waited weeks for a developer to build them." |
| Longed for | Early developer contact | "A developer in the critique once a month." |
The team links Lacked and Longed for. Experiment 1: invite one frontend developer to the next two critiques (owner: designer A). Experiment 2: share the date-filter learning with all product teams (owner: designer B). The lead checks both at the next retro.
Watch out for
- Rushing Learned. People find it harder to write. Give it the same time as the other columns, and give an example to start.
- Too many actions. A list of ten actions means none get done. Stop at 1–2 experiments with owners.
- Discussing before writing. If people talk first, the loudest view fills the board. Keep the writing silent.
- Not reviewing last time's experiments. Start each retro by checking the previous experiments, or the team stops believing in them.
Template
Copy this to your board or retro notes.
4Ls RETRO About 45 min
Looking back on: ___________________ Date: __________
Last retro's experiments: done? learned?
LIKED LEARNED LACKED LONGED FOR
(keep doing) (new insight) (missing) (wish we had)
- - - -
- - - -
Themes:
1.
2.
Experiments (owner, check date):
1.
2.