4 L's Retrospective Template
Reflect on what your team liked, learned, lacked, and longed for.
About the 4 L's Retrospective Template
The 4 L's retrospective is a team activity designed to understand what worked, what didn’t, and what can be improved upon following a sprint. The 4 L's stand for liked, learned, lacked, and longed for.
After a sprint, it can be helpful for the team to pause and take stock of what happened. Emotions can run high, so it can be difficult for teams to have a discussion that isn’t marred by frustration. The 4L's retrospective template is a useful retro tool that removes the emotional elements of a sprint. It empowers the team to highlight the positive elements of a sprint and understand the negative, allowing them to think from a factual rather than emotional perspective.
The 4L's technique is popular because it’s easy to understand and simple for a facilitator to set up. Unlike other traditional retrospectives, the 4 L's method requires only 30 to 60 minutes to complete.
How to run a 4 L's retrospective
One of the benefits of the 4 L’s retrospective is that it’s easy to set up and complete. Whether you’re using an online template to facilitate the retrospective online, or you plan on completing in person on a whiteboard, the following steps will help you succeed.
Step 1: Set the tone and expectations
Before starting the retrospective, make sure all participants understand its purpose. If the sprint being reflected on was stressful, consider addressing this openly and honestly before starting the retrospective. It is ultimately the facilitators job to set the tone and expectations for the activity, and it shouldn’t be taken lightly. The most successful retrospectives are completed when the team is fully bought into its importance and value, so the facilitator must take extra care to ensure this has happened before starting.
Step 2: Prepare the space
Whether you're holding your retrospective in person or online, the ‘space’ needs to be set up properly. Add the 4 L's retrospective template to your Miro board to begin setting up the space.
Step 3: Determine what was liked about the sprint
The first item in the 4 L's retrospective is intended to uncover what people liked about the sprint. This is intentionally broad and open ended. It’s up to the facilitator to guide participants into more and more useful insights into what they liked, and why they liked it. The goal is to uncover the underlying reasons for why a particular thing was liked, in order to ensure it happens again during the next sprint.
Step 4: Determine what was learned
The most valuable lessons are often learned from mistakes made, or challenges overcome during the completion of actual work. Unfortunately, these lessons often go unshared with the team. This is a wasted opportunity that the 4 L's retrospective is designed to capitalize on. This element of the retrospective asks participants to reflect on and share anything they might have learned.
It’s important for the facilitator to ensure the team understands no learning is too small to share, as well as to guide people into uncovering more learnings than they might have realized.
Step 5: Uncover what was lacked
This step is designed to surface everything that held the team back during the sprint. This can be something as simple as slow communication with an outside team, or something more complicated that requires extra analysis to uncover. The purpose of documenting what was lacked during a sprint is to make sure you don’t run into the same problem in future sprints.
It’s common for participants to feel uncomfortable sharing what was lacking if they feel leadership doesn’t want to hear about it. This might be because they believe the solution is too expensive or time consuming to be worth investing in. Either way, it’s again up to the facilitator to ensure the team feels comfortable sharing as much as possible during this step.
Step 6: Document what was longed for
The last element of the 4 L's retrospective involves reflecting on what was longed for. This can be something tangible like better equipment, or something less tangible, like more or less involvement from leadership.
Be careful that the ‘Longed for’ section isn’t simply a mirror of the what was lacked section. It will often be similar, but it gives you the opportunity to determine and prioritize what is needed based on the positive impact it may have. For example, if ‘faster computers’ was listed in the ‘Lacked’ section, ‘fast computers’ isn’t necessarily the only thing to add in this step. You might consider including ‘faster internet’ or ‘better software’ as other things that would solve for what was lacked.
Step 7: Assign followups and action items
This is perhaps the most important step in the retrospective process. If you don’t take the time to assign followup action items to specific people or teams, you won’t gain much from having completed the process.
Before ending the retrospective, ask for volunteers to own next steps. For any followup that doesn’t have a volunteer, assign it to the person most responsible for uncovering the insight during the retrospective. Close the session out by confirming everyone understand what is expected of them moving forward, and thank them for their time.
5 tips to a successful creating a 4L's retrospective
Running a successful retrospective takes careful planning and preparation. Here are some tips for making sure the meeting promotes team bonding and fosters a culture of open communication and continuous improvement:
1. Give people space and time to reflect
Make sure the team has about 30 to 60 minutes of uninterrupted time to take stock of their thoughts. Encourage people to take copious notes. Finally, make sure the room is quiet and free from outside distraction.
2. Ask everyone to turn off their devices so they can focus on the retrospective.
If people are distracted by their laptops or phones, then they will find it harder to reflect. If collaborating online using Miro to complete your 4 L's retrospective, consider asking people to have their cameras turned on to ensure they’re focused on the task.
3. Assure everyone that there are no right or wrong answers
The goal of the 4L's is to give your team the space they need to reflect after a sprint, so this isn’t a test! If participants feel like they’re unable to give honest feedback on what worked and what didn’t, the retrospective won’t uncover valuable insights. If you’re unsure about your team’s comfort level with giving honest feedback, consider making it anonymous. One benefit of performing a 4 L's retrospective online is that people have an extra layer of anonymity, and often are more willing to give critical feedback than when in person.
4. Encourage your team to focus on action, not emotion
The purpose of the 4 L's retrospective is to remove emotion from your judgement. The simple format is intended to facilitate objective feedback and reflection, but this can still be a challenge. If the sprint being evaluated was a particularly stressful one, consider a symbolic debrief activity to ease tension and lighten the mood before holding your retrospective. If you find the retrospective is becoming too emotional and not actionable, it’s the facilitators job to intervene and keep the discussion productive.
5. Use the 4Ls retrospective to bring remote teams together after a difficult sprint
Miro’s 4 L’s retrospective template gives remote and distributed teams the ability to collaborate without constraints. Remote teams often feel isolated, and the lack of a formal debrief and reflection after a particularly stressful sprint can harm morale. Hosting online retrospectives not only brings teams closer, but gives you the opportunity to find out what made that sprint challenging or stressful to ensure the next sprint runs smoother.
You can explore all sprint retrospective templates available through our collection.
Get started with this template right now.
OKR Drafting Board
Works best for:
Agile
The OKR Drafting Board (New) is a visual tool for defining and tracking Objectives and Key Results (OKRs). It provides a structured framework for setting ambitious goals, defining measurable outcomes, and aligning teams around shared objectives. This template enables organizations to articulate their strategic priorities, track progress transparently, and foster accountability and alignment across teams. By promoting focus, alignment, and agility, the OKR Drafting Board empowers organizations to achieve breakthrough results and drive continuous improvement.
Agile Board Template
Works best for:
Agile Methodology, Meetings, Agile Workflows
Part of the popular Agile framework, an Agile Board is a visual display that allows you to sync on tasks throughout a production cycle. The Agile Board is typically used in the context of Agile development methods like Kanban and Scrum, but anyone can adopt the tool. Used by software developers and project managers, the Agile Board helps manage workload in a flexible, transparent and iterative way. The Agile template provides an easy way to get started with a premade layout of sticky notes customizable for your tasks and team.
Meeting Agenda Template
Works best for:
Business Management, Meetings, Workshops
A detailed, clear agenda — that’s what separates meetings that go completely off the rails from those where goals are met and things get done. So grab this template and set a meeting agenda that lays out expectations for before, during, and after the meeting. It’ll enable participants to get prepared beforehand and empower you to stay on-task and identify when the discussion is complete. (Tip: Plan ahead to send out your meeting agenda at least 24 hours before the meeting.)
PI Planning Template
Works best for:
Agile Methodology, Strategic Planning, Software Development
PI planning stands for “program increment planning.” Part of a Scaled Agile Framework (SAFe), PI Planning helps teams strategize toward a shared vision. In a typical PI planning session, teams get together to review a program backlog, align cross-functionally, and decide on the next steps. Many teams carry out a PI planning event every 8 to 12 weeks, but you can customize your planning schedule to fit your needs. Use PI planning to break down features, identify risks, find dependencies, and decide which stories you’re going to develop.
Retrospective by Axelle Vanquaillie
Works best for:
Retrospectives, Agile Methodology
The Retrospective template facilitates team reflection and continuous improvement by providing a structured framework for evaluating past iterations or projects. It encourages open communication, identifies successes, challenges, and action items, fostering a culture of learning and collaboration. Team members can share feedback, insights, and suggestions, enabling them to celebrate achievements, address issues, and implement positive changes in future endeavors.
Lean Coffee by Michael de la Maza
Works best for:
Agile Methodology
Lean Coffee is a collaborative meeting format that encourages open dialogue and self-organization. Participants suggest discussion topics, vote on them, and engage in time-boxed conversations. This template provides a structured framework for facilitating Lean Coffee sessions, enabling teams to address issues, share knowledge, and make decisions collectively. By fostering inclusivity and autonomy, Lean Coffee empowers teams to drive meaningful discussions, build consensus, and drive continuous improvement.