4Ls Retrospective

Capture what was Liked, Learned, Lacked, and Longed For โ€” a balanced format that covers satisfaction, growth, gaps, and future desires.

What Is the 4Ls Format?

The 4Ls retrospective was created by Mary Gorman and Ellen Gottesdiener. It encourages teams to reflect on four distinct dimensions of their sprint experience, producing richer and more varied feedback than simpler formats.

๐Ÿ‘

Liked

What did the team enjoy or appreciate about this sprint? Positive experiences, tools, processes, or interactions worth recognizing.

๐Ÿ’ก

Learned

What new knowledge, skills, or insights did the team gain? Discoveries about the product, codebase, processes, or team dynamics.

๐Ÿ“‰

Lacked

What was missing that would have helped the team succeed? Resources, information, support, or clarity that wasn't available.

โœจ

Longed For

What does the team wish they had โ€” not just this sprint, but going forward? Aspirational improvements, tools, or changes to working practices.

Example Cards

๐Ÿ‘ Liked
The new CI pipeline โ€” deployments are so much faster
Team was very responsive in Slack this sprint
Clear acceptance criteria on most stories
๐Ÿ’ก Learned
Learned how the legacy authentication module works
Test coverage was much lower than we thought
Pairing with the backend team taught me a lot
๐Ÿ“‰ Lacked
Access to the staging environment for the first three days
A clear product vision for the roadmap items
Enough time for proper code review
โœจ Longed For
Better observability tooling โ€” we fly blind in production
A dedicated UX designer on the team
More time for refactoring and tech debt

Benefits of the 4Ls Format

  • Encourages knowledge-sharing โ€” the Learned column surfaces insights others may have missed
  • The Longed For column captures strategic improvements beyond sprint-level fixes
  • Balanced across positive, gap-finding, and aspirational thinking
  • Produces richer retrospective outputs than simpler three-column formats
  • Great for teams that value continuous learning and professional growth

Recommended Situations

  • Teams with moderate retrospective experience ready for more depth
  • After sprints with significant learning or technical exploration
  • When the team wants to identify longer-term improvements, not just sprint-level fixes
  • Quarterly or milestone retrospectives where deeper reflection is valuable
๐Ÿ› ๏ธ Need something different? BugNBrag's Scrum Master can add custom columns to any session โ€” so you can extend or adapt any template to fit your team's specific needs.

Run a 4Ls retrospective with your team

Select the 4Ls template in BugNBrag โ€” free, no account required.

๐Ÿš€ Create Free Session
An unhandled error has occurred. Reload ๐Ÿ—™

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.