4Ls Retrospective

Build a culture of openness and continuous improvement with the 4Ls, a retrospective technique in which team members identify what they loved, loathed, longed for, and learned from a project or sprint of work.

Prep time

5m

Run time

60m

Persons

2-8

People working together at the table

Prep time

5m

Run time

60m

Persons

2-8

Summary

  • Reflect on past key milestones.

  • Discuss the 4Ls for each milestone.

  • Document an action plan to improve.

What you will need

  • Video conferencing with screen sharing or meeting space.

  • Digital collaboration tool (see templates).

  • Optional: physical whiteboard, markers, sticky notes, and timer.

How to run a 4Ls Retrospective

Build a culture of openness and continuous improvement with the 4Ls, a retrospective technique to identify what you loved, loathed, longed for, and learned from a project or sprint of work.

What is a 4Ls retrospective?

A 4Ls retrospective is a structured feedback technique used by teams to reflect on a completed sprint or project so they can improve future projects.

The "4Ls" stand for Loved, Loathed, Longed for, and Learned. Here's what each of them represents:

  • Loved: What went well during the project? These are the things that team members appreciated, enjoyed, or found to be effective.

  • Loathed: What made things worse? What was missing or needs improvement? This category identifies gaps, such as missing resources, skills, or support that would have made the sprint more successful.

  • Longed for: What do team members wish they’d had during the sprint? This could be anything that would have made the work more efficient or enjoyable, like better tools, clearer requirements, or more time.

  • Learned: What new knowledge or skills did the team gain? This could be technical knowledge, better communication methods, or insights into the project or process.

Why run a 4Ls Retrospective Play?

Retrospectives promote continuous learning, helping teams refine workflows and techniques, and ensure more effective project delivery in the future. Research shows that teams practicing regular retrospectives are 24% more responsive, have 42% higher quality, and less variable than those with infrequent or no retrospectives.

When should you use a 4Ls retrospective?

The 4Ls retrospective can be adapted to different team dynamics, project phases, and time frames. It’s not limited to just the end of a sprint or tech teams; it can also be used formally at the end of a project, a release, or significant events or impromptu to improve team meetings.

3 benefits of the 4Ls retrospective

  • Balanced feedback: The 4Ls framework encourages a balanced reflection by covering both positives and areas for improvement.

  • Action-oriented: The 4Ls framework pinpoints specific areas that need improvement, making it easier to create targeted action plans for future sprints.

  • Positive framing: The 4Ls framework maintains a constructive tone during the retrospective, focusing on opportunities rather than just problems.

Still have questions?

Start a conversation with other Atlassian Team Playbook users, get support, or provide feedback.

Plays you may like

Meetings

Weekly Team Updates

Share how things are going—without scheduling another meeting.

Meetings

Page-Led Meetings

Better meetings start with a page.

Communication

My User Manual

Help your teammates understand how best to work with you.

Debriefs

Retrospective

Provide a safe space to discuss what worked and what didn’t.

Stay up to date

Get the latest Plays and work life advice when you sign up for our newsletter.

Stay up to date

Get the latest Plays and work life advice when you sign up for our newsletter.