4Ls Retrospective
Liked, learned, lacked, and longed for—structured reflection that surfaces both positives and gaps.
Liked
What did you genuinely enjoy or appreciate this iteration?
Learned
Insights, surprises, or skills gained—technical or interpersonal.
Lacked
What was missing? Support, clarity, time, documentation, or tooling.
Longed for
What do you wish had been true? Aspirations for the next cycle.
This board is for demo purposes only. Your responses are not saved. Close or refresh the page to clear all cards. Do not add any sensitive information.
What is the 4Ls Retrospective?
The 4Ls Retrospective—Liked, Learned, Lacked, and Longed For—is a structured reflection format that balances emotional expression with practical observation. The framework was popularized by Mary Gorman and Ellen Gottesdiener in the agile community as a way to capture a fuller picture of the team experience. The alliterative structure makes it memorable and easy to facilitate, even for first-time retrospective leaders.
Each L targets a different dimension of the sprint experience. "Liked" captures positive emotions and practices that energized the team. "Learned" surfaces new knowledge, skills, or insights gained during the iteration. "Lacked" names concrete gaps—missing resources, unclear requirements, or insufficient support. "Longed For" invites aspirational thinking about what the team wishes had been true.
What makes the 4Ls unique compared to simpler formats is the explicit separation of learning from liking. A team might learn something valuable from a painful experience—separating these encourages nuanced reflection. The "Longed For" column adds a forward-looking dimension that most retrospective formats miss, bridging the gap between looking backward and planning ahead.
When to use the 4Ls Retrospective
The 4Ls is ideal for teams that are past the initial forming stage and ready for deeper reflection. It works particularly well after a sprint where significant new territory was explored—a new technology adoption, a complex integration, or a shift in team composition. These situations generate rich material for the "Learned" column that simpler formats would miss.
This format suits teams of four to ten people and works in 45 to 60 minute sessions. It is especially effective for cross-functional teams where designers, developers, and product managers bring different perspectives on what was liked, learned, or lacking. The four distinct categories give each discipline a natural entry point for their unique observations.
Use the 4Ls when your team tends to focus only on problems and needs a format that explicitly encourages positive reflection and growth recognition. Avoid it if the team is in crisis mode and needs rapid action items—the contemplative nature of "Learned" and "Longed For" may feel indulgent when urgent problems demand immediate attention.
How to facilitate the 4Ls Retrospective
Start with a one-minute explanation of each L, giving an example for each to calibrate expectations. Then set a timer for seven minutes of silent individual writing. Encourage participants to aim for at least two cards per column. Having a minimum prevents people from loading one column and ignoring others.
Process the columns in order: Liked first to establish positive energy, then Learned to celebrate growth, then Lacked to surface gaps, and finally Longed For to look ahead. For each column, have participants read their cards aloud, group related items, and allow brief discussion. Resist deep-diving on every item during the read-through phase.
After all four columns are populated, ask the team to identify connections across columns. Often something that was "Lacked" directly maps to something "Longed For," which creates a natural action item. Dot-vote on the most impactful themes, then spend the final fifteen minutes crafting two to three concrete action items with owners. Close by asking each person to name one thing they learned during the retro itself.
Tips for getting the most out of the 4Ls Retrospective
The "Learned" column is the differentiator of this format, so invest facilitation energy there. Push beyond surface-level observations like "I learned React hooks" to deeper insights like "I learned that pairing with someone outside my expertise for the first hour of a new task saves me days of rework later." These meta-learnings about how the team works are where the real value lives.
A common pitfall is treating "Longed For" as a complaint column in disguise. "I longed for better requirements" is just "Lacked" rephrased. Coach participants to think aspirationally: "I longed for a weekly 15-minute sync with the design team to review upcoming work." The distinction between lack and aspiration is crucial for generating constructive rather than defeatist energy.
Watch for uneven column sizes. If "Liked" is empty, the team may be demoralized and needs a morale-focused intervention beyond the retro. If "Lacked" dominates, consider whether the team has the agency to fix the identified gaps or whether escalation to leadership is needed. Column balance is a diagnostic tool.
Variations and adaptations
For remote teams, use a virtual whiteboard with color-coded sticky notes for each L. Enable anonymous submissions for the "Lacked" and "Longed For" columns if the team is still building trust. Remote facilitation benefits from a designated note-taker who captures key discussion points in a shared document alongside the board.
For async retros spanning multiple time zones, open the board with clear instructions and examples 48 hours before a synchronous wrap-up session. Ask each person to add at least two items per column and to leave a reaction or comment on at least three items from others. The synchronous session then focuses on synthesis, voting, and action planning rather than card generation.
A popular adaptation for teams focused on professional development is to make "Learned" the centerpiece. Spend 50 percent of the retro time on that column, exploring what was learned, how it was learned, and how to share that knowledge with the broader organization. This variation works well quarterly as a learning-focused retrospective that complements your regular sprint retros. Some teams also add a fifth L—"Loved"—to create space for celebrating exceptional moments.
Run Retrospectives in CodeKudu
CodeKudu includes dozens of retrospective board templates, anonymous feedback, AI summaries, and action items that sync to GitHub Issues, Jira, and Linear.
