4Ls Retrospective: Deeper Team Learning
The 4Ls Retrospective gives managers a structured way to surface not only what worked and what fell short, but what the team learned and genuinely aspires to…
Topic: Teamwork & Collaboration
Why It Matters
Team reviews often end with a list of action points and a collective sigh of relief. The meeting is done, the items are captured, and everyone moves on. But if the only question your team is answering is "what do we fix?", you are leaving a significant portion of your team's insight, energy, and aspiration on the table.
The 4Ls Retrospective is a structured reflection format that asks teams to consider four dimensions:
what they Liked,
what they Learned,
what they Lacked, and
what they Longed For.
It is widely used in project management, team development, and Agile contexts, but its value extends well beyond sprint cycles. Managers running quarterly reviews, post-project debriefs, or annual team health checks will find it equally applicable.
What makes it distinctive is the emotional range it covers. Most retrospective formats focus on performance outcomes. This one also surfaces aspiration and growth, giving teams a shared language for expressing both satisfaction and unmet potential.
Before reading further, consider whether any of the following apply to your situation.
Does your current review process feel more like a fault-finding exercise than a genuine conversation?
Are your team members hesitant to speak honestly in retrospectives, or do discussions tend to circle back to the same themes without producing anything new?
Have you recently completed a project or significant phase where you sensed the team had more to say than the debrief captured?
If any of these resonate, the 4Ls format is worth your attention.
Origin and Underlying Logic
The 4Ls format was developed by Mary Gorman and Ellen Gottesdiener, practitioners in requirements and product development, as a way to bring more nuance to team retrospectives.
It builds on the retrospective tradition popularised by Agile methodologies, but its underlying logic is grounded in reflective learning theory: the idea that sustainable improvement requires more than identifying problems.
It requires understanding what energised the team, what knowledge was generated, what fell short, and what the team genuinely hopes for next time.
The framework reflects a simple but powerful premise: teams perform better when they feel heard across the full spectrum of their experience, not just the operational dimension.
Related frameworks include the traditional Start/Stop/Continue format, the Plus/Delta model, and the retrospective structures associated with established Agile practice.
The 4Ls sits within this family but addresses a gap that most alternatives leave open: the aspiration dimension, through Longed For, which none of the common alternatives explicitly capture.
Structure and Application
The 4Ls works by creating four distinct reflective spaces within a single conversation. Each dimension serves a specific purpose, and the sequence matters.
"Liked" captures what worked well and what generated positive energy. This is not simply a list of successes; it is an invitation to surface the conditions, behaviours, and dynamics that the team would want to preserve or repeat. Starting here sets a constructive tone and ensures the session does not open with complaint.
"Learned" asks what knowledge, insight, or capability the team gained during the period under review. This can include lessons that emerged from things that went wrong, as well as unexpected discoveries from things that went right. It positions failure as a source of value rather than a source of shame, which tends to open up more honest contribution.
"Lacked" surfaces what was missing: resources, clarity, communication, support, or skills. This is the most action-oriented quadrant, but it benefits from being positioned after Liked and Learned rather than at the start of the conversation. By the time the team reaches Lacked, they have already established a balanced perspective and are less likely to slide into blame.
"Longed For" is the dimension that distinguishes this format from most alternatives. It invites team members to express genuine aspiration: what they wish had been in place, what kind of environment or support they hope for in future, and what would make the work more meaningful or effective. It is often where the most important feedback lives, and it is the quadrant most likely to generate insight that no other format would have surfaced.
The format typically takes the shape of a four-quadrant whiteboard or digital canvas, with participants adding responses (usually on sticky notes) to each quadrant independently before discussing patterns as a group.
It is most effective at the team level, though it can be adapted for one-to-one development conversations or cross-functional reviews. Teams of between four and twelve people tend to generate the richest discussions; larger groups require more facilitation structure to keep the session productive.
Before your next team review, draft two or three tailored prompts for each of the four quadrants, specific to the work period you are reviewing.
Starting with prepared prompts rather than open-ended questions significantly improves the quality of contributions and signals that the session has been prepared thoughtfully.
That said, designing prompts that open up honest reflection without inadvertently narrowing what the team feels safe to say is a facilitation skill in itself, and it is one the deep dive addresses directly.
FAQ
Q: What is the 4Ls retrospective?
A: The 4Ls Retrospective is a structured team review format that guides reflection across four categories: Liked, Learned, Lacked, and Longed For. It is designed to capture a fuller range of team experience than traditional action-focused retrospectives, including what energised the team, what knowledge was gained, what fell short, and what the team genuinely aspires to in future work.
Q: How is the 4Ls retrospective different from Start/Stop/Continue?
A: Both are structured retrospective formats, but they serve different purposes. Start/Stop/Continue is primarily action-oriented, focused on which behaviours should change going forward. The 4Ls adds a learning and aspirational dimension through Learned and Longed For, making it better suited to teams wanting to deepen reflective practice rather than simply generate a task list. If your retrospectives feel mechanical or repetitive, the 4Ls is worth the additional investment in facilitation time.
Q: How long does a 4Ls retrospective take?
A: For a team of four to eight people reviewing a typical project phase, allow sixty to ninety minutes. Larger groups or longer review periods may need two hours. The most common timing mistake is underestimating the discussion phase: once contributions are on the board and themes are clustered, the conversation tends to go deeper than expected, which is often exactly what you want.
Q: How do I know if the 4Ls retrospective is right for my team?
A: It tends to be most valuable after a meaningful shared experience, when you sense there is more to surface than a standard debrief would capture. It is also particularly useful with teams where psychological safety is still developing: the Liked and Longed For categories give people a way into the conversation that does not require them to lead with criticism. If your current retrospectives feel perfunctory or produce the same outputs each time, the 4Ls format is a strong candidate for a reset.
Q: Can the 4Ls retrospective be used outside of Agile or project management contexts?
A: Yes. While the format originated in Agile and product development circles, it transfers well to any team-level review: annual health checks, end-of-quarter reflections, post-event debriefs, or individual performance conversations adapted for a coaching context. The structure is flexible enough to apply wherever you want to move beyond surface-level feedback and create space for something more substantive.