4Ls Retrospective Template: Liked, Learned, Lacked, Longed For

Introduction

A good retrospective template gives the team enough structure to think clearly without forcing a predetermined answer. The format encourages reflection beyond success and failure.

This guide explains the approach in practical terms: what it is, why it is useful, when to use it, how to apply it step by step, and which mistakes to avoid.

What is it?

The 4Ls retrospective organizes feedback into Liked, Learned, Lacked, and Longed For. Liked captures positive experiences, Learned records new knowledge, Lacked identifies missing resources or conditions, and Longed For explores improvements participants wanted.

Why is it useful?

The format encourages reflection beyond success and failure. It makes learning visible and distinguishes something that was absent from something the team hopes to create. This is valuable after discovery work, launches, workshops, and projects with substantial uncertainty.

Benefits

• Highlights learning as a first-class outcome.
• Separates missing necessities from future aspirations.
• Balances positive reflection with improvement needs.
• Produces rich qualitative insight for complex work.

When should you use it?

Use the 4Ls after a project phase, release, experiment, training, discovery sprint, or any cycle where learning matters as much as delivery. It is also useful when standard formats are generating shallow or repetitive responses.

How to do it

1. Define the reviewed period. Give participants a shared boundary so cards refer to the same experience.
2. Write Liked cards. Capture moments, practices, decisions, or interactions that created value.
3. Write Learned cards. Record new facts, validated assumptions, changed beliefs, and skills gained.
4. Write Lacked and Longed For cards. Separate essential missing conditions from desired improvements or opportunities.
5. Find relationships. Look for links, such as a learning that explains what was lacked or a liked practice that should be expanded.
6. Prioritize and act. Vote on the themes and choose one improvement or learning application for the next cycle.

Real example

After a customer discovery sprint, a team Liked direct interview access, Learned that buyers and daily users had different goals, Lacked consistent note tagging, and Longed For faster access to usage data. The team chose an action to create a shared research-tag system and a request to connect product analytics before the next discovery cycle.

Common mistakes

• Using Learned only for technical knowledge and ignoring customer or process learning.
• Writing the same problem in Lacked and Longed For without clarifying the distinction.
• Spending equal discussion time on every column.
• Failing to apply the captured learning to future decisions.

FAQ

What is the difference between Lacked and Longed For?

Lacked is something the team needed but did not have. Longed For is a desired condition, capability, or opportunity that may not have been essential.

Can the 4Ls be used for personal reflection?

Yes. The categories also work for individual learning reviews and coaching conversations.

How many cards should each person add?

Two or three per column is usually sufficient. Quality matters more than volume.

Conclusion

The 4Ls create a richer picture of work by capturing experience, knowledge, gaps, and aspirations. Use the relationships between columns to identify the most valuable next change.

Call To Action

Launch a 4Ls retrospective in SprintsPlans and let the team prioritize which learning, gap, or desired improvement should shape the next sprint.