3 L's

A lightweight three-column retrospective for teams that want quick, honest feedback. Participants capture what they liked, what they learned and what they lacked during the sprint. Stripped down to the essentials, it's an easy starting point for teams new to retrospectives or short on time.

What you appreciated about the sprint

Roman

Liked the shorter planning — 45 minutes was enough

Maria

Liked that support joined the demo

Learned

New knowledge — about the product, the system or the team

Anna

Learned the cache invalidation was the root of both bugs

Daria

Learned that half the team had never seen the deploy script

Lacked

What was missing: information, time, access or a decision

Maria

Lacked a decision on the API version before we started

Kirill

Lacked test data that looks like real accounts

Try Template

The 3 L's template is a simple yet effective retrospective tool that helps teams reflect on their sprint or project performance. It consists of three columns: "Like," "Learned," and "Lacked." The purpose of this template is to identify what worked well, what was learned, and what can be improved upon.

Column 1: Like

This column is for listing what the team felt went well during the sprint or project. Examples of what could go in this column include:

Effective communication between team members
Smooth collaboration on a particular task
High-quality work produced during the sprint

Column 2: Learned

This column is for listing what the team learned during the sprint or project. This can include lessons learned from challenges faced, new skills acquired, and any other knowledge gained. Examples of what could go in this column include:

A new tool was discovered that improved efficiency
A team member learned a new coding technique
The team learned about a new project management method

Column 3: Lacked

This column is for listing what the team felt was lacking during the sprint or project. This could be areas for improvement or any obstacles encountered. Examples of what could go in this column include:

Lack of resources or tools needed to complete a task
Difficulty in communication with a stakeholder
Limited time to complete a task

By reflecting on what was liked, learned, and lacked, teams can identify areas for improvement and make changes to increase their efficiency and success in future sprints or projects.

Similar templates

Other formats teams pair with this one — open any of them as a board in one click.

DAKI

DAKI gives the team four clear levers for change in a single view. Participants decide what to drop because it no longer helps, what to add that's missing, what to keep that works well and what to improve. The crisp structure makes it easy to leave the session with a concrete, balanced set of adjustments.

SWOT Analysis

A strategic format borrowed from business analysis and adapted for team reflection. The team maps its strengths and weaknesses against external opportunities and threats to see the bigger picture. It works especially well for longer horizons — a quarter, a release or a project — where strategy matters as much as day-to-day fixes.

The Good - The Bad - The Ugly

A vivid three-part format that makes room for things the team can't simply fix. The good is what worked well, the bad is what went off plan, and the ugly is what lies outside the team's control but still deserves to be named out loud. That third column is what sets it apart, surfacing systemic issues that other formats tend to skip.

Agile Kanban

A retrospective that borrows the familiar Kanban board to review the team's flow of work. Items move across to do, doing and done, making bottlenecks and stalled tasks easy to see. It's a natural fit for teams that already think in terms of flow and want their reflection to mirror how they actually work.

Six Thinking Hats

Based on Edward de Bono's method, this format has the team look at the sprint through six distinct mindsets. Each hat directs attention to one angle — facts, feelings, caution, optimism, creativity and process — so the discussion stays balanced and no perspective is missed. It's a powerful way to break out of habitual thinking and explore an issue from every side.

Post Mortem Retro

A reflective format for looking back on a finished project or major milestone. The team gathers what it liked, what it missed, what individuals learned and what to do differently next time, closing with appreciations. The wider lens makes it ideal for drawing lasting lessons rather than tweaking the last sprint.

Try Template