Building a 4Ls Retrospective Board and Template

Build a reusable 4Ls retrospective board and template, physical or digital, with prompts, voting space and an action area the team reuses.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

A 4Ls retrospective board is the workspace where the team writes, sorts and votes on its feedback. A good board does part of the facilitator's work: it tells people what each category means, where to put a note that fits nowhere, how voting works and where the actions go. A bad board is four empty boxes, which leaves every question to be answered out loud and wastes the first ten minutes of the meeting. The method page explains the categories themselves; this skill is about the physical or digital layout that holds them.

The original layout was physical. Mary Gorman and Ellen Gottesdiener's EBG write-up hangs four posters around the room, one per L, so people walk to each poster to post notes and later split into subgroups, one per poster. Ben Linders describes the same idea with flip charts, and notes that a shared editable document works for distributed teams. Today most teams use a digital board even when co-located, because it keeps a record without anyone photographing sticky notes.

Build the board once as a template, then copy it each sprint. A template keeps the layout consistent, which matters later when someone wants to compare themes across many retrospectives. It also lowers the preparation cost to a few minutes: copy, update the sprint facts, set the prompts, and share the link.

How It Works

The board has to support each phase of the meeting, so design it phase by phase. The five phases from Derby and Larsen's Agile Retrospectives map onto areas of the board.

Columns or quadrants both work. A four-quadrant grid keeps all categories visible at once and suits a wide screen or wall. Four side-by-side columns leave more vertical space for notes and are easier to scan left to right. Put the categories in the order Liked, Learned, Lacked, Longed For, which starts the team on what went well and ends on what it wants.

Prompts go at the top of each column. One or two short questions per category are enough; FunRetrospectives offers examples such as "What aspects of our work did you really enjoy?" for Liked. Prompts cut down on miscategorized notes and on blank stares.

Voting needs its own rules on the board. The Nielsen Norman Group recommends giving each person about a quarter as many votes as there are options, and voting silently. On a digital board, use the tool's hidden-voting feature if it has one, so people cannot see where others' dots went before they vote.

The action area is the part most boards get wrong. It needs fields for the action, one owner and a date, and it should sit where everyone sees it at the close, not in a corner.

Step-by-Step Guide

Step 1: Choose the Medium

Pick physical or digital based on where people sit, not on habit. If everyone is in one room, posters or a whiteboard make the session more active, as in the EBG layout. If anyone is remote, use a digital board for everyone, so remote people are not reading a camera view of a wall. Check that the tool supports anonymous notes, hidden voting and export, because each of those comes up later. Choose one tool and stick with it, since switching loses the history.

Step 2: Lay Out the Four Categories

Create four equal areas labelled Liked, Learned, Lacked and Longed For, in that order. Give each area a distinct background color and use the same color every sprint, so people learn the layout. Leave enough room in each area for clusters to grow, since Lacked usually fills fastest. Add a small "Not sure where this goes" area beside the four, which stops people from agonizing over placement during silent writing. Keep labels large enough to read from across the room or on a laptop screen.

Step 3: Add Prompts to Each Category

Write one or two questions at the top of each area. Keep them short and concrete: "What would you want to do again next sprint?" is easier to answer than "What did you like?" Use the FunRetrospectives prompts as a starting point and adjust them to the sprint. For Lacked and Longed For, add one line that clarifies the difference: Lacked is what was missing, Longed For is what you wish you had next. Leave the prompts editable in the template so each facilitator can tune them.

Step 4: Build the Header

Across the top, add the sprint name and dates, the sprint goal and whether it was met, and a short list of what shipped. Include last retrospective's actions with a status field for each. Add the working agreement or a paraphrase of the Prime Directive so the tone is set before anyone writes. The header gives people facts to react to, which makes notes more specific. Keep it short enough to read in a minute.

Step 5: Add Clustering and Voting Space

Inside each category, leave room to drag notes into groups, with a place to write a theme name above each group. Add a legend that explains the voting rules: how many dots each person gets and whether they can stack them. If the tool supports it, set up a voting session with results hidden until everyone is done. On a physical board, use sticky dots and ask people to vote at the same time. Put the vote count next to each theme name so the ranking is visible.

Step 6: Add the Action Area

Create a table or column labelled Actions with fields for the action, the owner and the due date. Place it to the right of or below the four categories, where people naturally look at the end. Add a note that each action needs one named person, not "the team". Include a small parking area for topics raised but not discussed, so they are not lost. Link or copy actions from here into the sprint backlog before the meeting ends.

Step 7: Save as a Template and Test It

Save the board as a template in your tool, with prompts, legend and empty action table in place. Run a quick dry run with one or two teammates to catch confusing labels or cramped areas. After the first real retrospective, ask what was confusing about the board and fix it in the template, not only in that sprint's copy. Keep an archive of finished boards with a consistent naming scheme, which makes trend tracking possible later. Review the template every few months rather than every sprint.

Best Practices

• Keep the same layout, colors and order every sprint. Consistency lets people focus on content instead of finding their way around, and it makes old boards comparable.
• Put prompts on the board itself rather than only saying them aloud. People look at the board while writing, and written prompts reduce miscategorized notes.
• Turn on anonymous notes when trust is uncertain. Anonymity is easy to switch off later once the team is comfortable, and hard to recover once someone has been singled out.
• Hide votes until everyone has voted. Visible votes pull later voters toward early leaders, which the Nielsen Norman Group lists as a common dot-voting failure.
• Make the action area impossible to miss. If it is small or off to the side, the meeting tends to end without filling it.
• Archive every finished board with the date and sprint name. The archive is the raw material for any later look at recurring themes.

Common Mistakes

• Four empty boxes with no prompts: People stall or put notes in the wrong place. Add one or two concrete questions to each category and a short line on the Lacked and Longed For difference.
• No place for actions: Boards that stop at the four categories end meetings with themes and no commitments. Add an action table with owner and date fields as a fixed part of the template.
• Rebuilding the board from scratch each sprint: This wastes preparation time and makes boards inconsistent. Save a template and copy it.
• Too much decoration: Icons, stickers and instructions everywhere compete with the notes. Keep the board plain and let the content stand out.
• A physical board for a hybrid team: Remote people cannot read or move notes on a wall. Use a digital board for everyone whenever even one person is remote.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: 4Ls Sprint Retrospective

Related Skills

• Facilitating a 4Ls Sprint Retrospective Meeting
• Tracking 4Ls Retrospective Trends Across Sprints
• Sorting Team Feedback into the 4Ls Categories
• Writing 4Ls Retrospective Questions for Each Category
• Turning 4Ls Retrospective Insights into Action Items
• Running a 4Ls Retrospective for Remote and Hybrid Teams

Sources

• EBG Consulting: The 4L's, a retrospective technique
• Ben Linders: Four L's, a classic retrospective exercise
• FunRetrospectives: 4 Ls
• Derby, Larsen and Horowitz: Agile Retrospectives, Second Edition
• Nielsen Norman Group: Dot voting
• Retrospective Wiki: The Prime Directive

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.