The 4Ls Retrospective: Loved, Loathed, Longed For, Learned
The 4Ls retrospective is a structured way to capture a team's feelings after a project. It asks what they Loved, Loathed, Longed for, and Learned to create an action plan. A common pitfall is only focusing on negatives, missing key insights from the other Ls.
The mental model
The 4Ls retrospective is a structured technique for capturing team feedback that balances positive, negative, and forward-looking insights. Instead of just asking "what went wrong?", it uses four distinct prompts—Loved, Loathed, Longed for, and Learned—to foster a culture of openness and drive continuous improvement.
How it works
A facilitator guides the team through reflecting on a recent project or sprint. Team members silently write down their thoughts for each of the four categories. First, what they Loved (positive experiences or outcomes). Second, what they Loathed (pain points and frustrations). Third, what they Longed for (what was missing that would have helped). Fourth, what they Learned (new insights or discoveries). The team then shares their notes, groups similar items, and discusses them. The final step is to create a documented action plan to address the key takeaways.
When to use it
Use the 4Ls at the end of a sprint or project to gather holistic feedback. It is particularly effective for small-to-medium-sized teams (2-8 people) and helps build psychological safety by explicitly making space for positive reinforcement ("Loved") alongside constructive criticism.
When not to use it
This format may be less effective for very large groups unless they are split into smaller breakout sessions. It is also not a substitute for a deep-dive technical post-mortem, as its focus is more on team process and sentiment rather than a formal root cause analysis of a major incident.
One canonical example
A software team finishes a sprint. In the 4Ls retro, one engineer shares they LOVED the new CI pipeline. Another LOATHED a last-minute scope change. A designer LONGED FOR earlier involvement in feature planning. The team LEARNED that pair programming on a complex bug was highly effective. From this, they create two action items: first, to define a stricter process for scope changes, and second, to invite the designer to their next sprint planning meeting.
Interview question
What is a primary benefit of the 4Ls retrospective compared to only discussing "what went wrong"?
- a.It provides a holistic view by incorporating positive experiences and future needs.Correct
- b.It focuses solely on technical issues, leading to more precise solutions.
- c.It guarantees anonymity for all feedback, promoting honesty.
- d.It is primarily designed for very large teams to conduct formal root cause analysis.
Why? this is the answer
The 4Ls retrospective explicitly balances positive, negative, and forward-looking insights through its 'Loved' and 'Longed for' categories, offering a holistic view beyond just problems. It is noted as less effective for very large groups and not a substitute for deep-dive technical root cause analysis.
Just read this? Test yourself on what you have been reading.
Read the original → atlassian.com
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles