Liked 😊
What was helpful and worked well?
Example cards
- The team collaboration tools streamlined our communication.
- Daily stand-ups kept everyone updated on progress.
- The new onboarding process helped new members get up to speed quickly.
4Ls Retrospective
A structured reflection session to retain successful practices, gather new knowledge, and identify team needs post-release or phase completion.
45–60 min4–12 people4 columns
Adjust the columns and settings before you start.
Created by Alexandr Voloshyn
OfficialRecommended
Find the right fit
When to use it
Use this when you want to gather team feedback on both past workflows and future improvements.
When to choose another format
Avoid if the team is not ready for open feedback or if the meeting is rushed without adequate preparation.
Questions that guide the conversation
Use these prompts to collect specific observations. One idea per note keeps the discussion easy to follow.
Learned 📚
What knowledge or conclusions did we gain?
Example cards
- We discovered the importance of early user feedback.
- Not all features planned initially are necessary for the final product.
- How to better estimate our tasks and timelines.
Lacked 🚫
What essential resources or support were missing?
Example cards
- We lacked sufficient documentation for new tools.
- There was insufficient clarity on roles within the project.
- Technical resources were not available when needed.
Longed For 🌟
What new capabilities would improve the next cycle?
Example cards
- A dedicated training session on advanced tools would be beneficial.
- Access to analytics tools to measure user engagement better.
- More regular brainstorming sessions to foster innovation.
From reflection to a next step
45–60 minA suggested flow for this board. Reserve time at the end to agree on what happens next.
- 1
Introduction 5 min
Explain the purpose of the retrospective and how it will be conducted.
- 2
Column Discussion: Liked 10 min
Gather insights on positive outcomes and helpful practices from the last cycle.
- 3
Column Discussion: Learned 10 min
Discuss new knowledge gained and insights or conclusions from the recent work.
- 4
Column Discussion: Lacked 10 min
Identify needed resources, information, or support missing during the last phase.
- 5
Column Discussion: Longed For 10 min
Explore desired capabilities or improvements for future cycles.
- 6
Action Items 10 min
Identify and prioritize 1-2 actionable experiments for the next cycle and decide ownership.
Facilitator’s example
Make the next step small enough to happen
A specific observation
The team identified recurring issues about communication gaps in the last release cycle.
A clear experiment
Assign a communication champion who will ensure all team members are regularly updated on project status. Responsibility: Sarah; Timeline: 2 weeks; Result: Measure improvement in communication satisfaction through a quick survey.
Make the conversation useful
- Encourage open communication to foster psychological safety.
- Remind participants of the key differences between Lacked and Longed For before the discussion.
- Use concrete examples to illustrate points and facilitate engagement.
Before you start
What if the team is hesitant to provide feedback?
Reassure them that all feedback is valuable and will be treated constructively.
How detailed should we be in the discussions?
Focus on specifics; even small observations can lead to significant insights.
Can we use this format for non-sprint retrospectives?
Yes, this format can be adapted for any phase or project retrospective.
What do we do if the discussions are dominated by a few voices?
Encourage participation by directly inviting quieter members to share their thoughts.
More retrospective templates
All templatesOfficialRecommended
OfficialRecommended
OfficialRecommended