4Ls Retrospective

4Ls retrospective

The 4Ls retrospective—Liked, Learned, Lacked, and Longed For—offers teams a structured way to reflect on recent projects or sprints by covering four unique aspects.

This approach captures both positive experiences and areas for improvement, balancing insights about current practices and aspirations for future growth.

What is 4Ls: Liked, Learned, Lacked, and Longed For

The 4Ls retrospective technique encourages open discussion around the team’s recent experiences by categorizing reflections into four sections:

Liked

Liked

Things you liked, enjoyed or appreciated.

This category allows team members to express what they genuinely enjoyed about the recent project or sprint. It includes aspects of the workflow that were efficient, positive team interactions, tools that boosted productivity, or any achievements that created a sense of accomplishment.

Focusing on “Liked” encourages teams to recognize their strengths and continue successful practices.

Learned

Learned

What did you learn during this iteration or sprint?

Here, team members share valuable lessons gained during the project. “Learned” covers insights about the process, technical skills, or interpersonal dynamics that contributed to growth. This category encourages knowledge-sharing within the team, enabling everyone to understand and apply each other’s insights in future sprints.

Examples can range from learning about new coding practices to improving communication strategies with stakeholders.

Lacked

Lacked

What was missing in the last iteration or sprint?

This section highlights resources or conditions that were insufficient during the project. Team members discuss missing tools, knowledge gaps, or support that could have improved performance.

This feedback helps identify bottlenecks and allows managers to make necessary adjustments for future projects, such as increasing access to resources or providing training.

Longed For

Longed For

What was the thing that had you thinking, “If only we had…”?

“Longed For” adds a forward-looking element, where team members share what they wish had been available during the sprint. These could be improvements in team structure, resources, or any changes to boost future performance.

Addressing the “Longed For” items helps the team set realistic goals and plan for future projects with a more supportive environment in mind.

The 4Ls retrospective framework ensures that team members have a balanced and inclusive space for sharing both achievements and challenges, helping teams foster an open culture of continuous improvement.

When to Use a 4Ls Template?

The 4Ls retrospective is versatile and effective across various scenarios, from sprint reviews to larger project evaluations. Here are some ideal times to use this framework:

  • After Major Changes or New Processes: If the team has implemented a significant change—such as new technology, a revised workflow, or restructured team dynamics—the 4Ls template can help assess the impact. It captures a wide range of insights, giving teams a clear view of what’s working and what requires fine-tuning.

  • During Long-Term or Complex Projects: For lengthy projects with multiple phases, the 4Ls retrospective breaks down complex experiences into manageable insights. This approach can help teams track progress across each project stage, identifying successes to continue and challenges to address in the following phases.

  • Regular Sprint Retrospectives: The 4Ls template also suits regular sprint reviews, as it doesn’t demand immediate solutions but instead facilitates honest, constructive discussions. This format is less pressuring, allowing teams to explore different ideas and look beyond immediate fixes to longer-term improvements.

How to Run a 4Ls Retrospective with AgileBox

AgileBox makes it easy to organize 4Ls sessions, especially with remote or hybrid teams. Here’s a simple guide to running one:

Access the Retrospective Section

In AgileBox, go to the Retrospective section and select “Add Meeting.” This will prompt you to create a new session for your team.

Choose the Liked, Learned, Lacked, and Longed for Template

AgileBox provides pre-made templates, including 4Ls, which categorize feedback into four areas—Liked, Learned, Lacked, and Longed for.

4Ls retrospective

Follow the Retrospective Steps

AgileBox organizes the meeting into four stages:

  • Reflect: Team members individually add items under the 4Ls. This stage allows for independent reflection and is often done anonymously to encourage honesty.

  • Group: Next, similar feedback items are grouped. This process helps identify common themes, making it easier to focus discussions on the most significant topics.

  • Vote: Team members then vote on the grouped items to prioritize key issues. The items with the most votes are typically the most pressing or valued by the team.

  • Discuss: Finally, discuss the top-voted items. This conversation is guided, encouraging solutions for the “Lacked” and “Learned” points and a strategy to build on the “Liked” and “Longed For” moments.

4Ls retro template

Using AgileBox’s 4Ls template, teams can efficiently capture and analyze feedback, resulting in clearer insights and actionable improvements for future projects.

Improve your agile process with AgileBox

Free for 30 days on Atlassian Products!
Always free for under 10 users instance on Jira Cloud
Menu