Works with Claude, ChatGPT, Gemini, or your own local model: paste this prompt and your AI will co-facilitate this exercise with you.

Help me prepare and run the exercise below. First ask for my participant count, time, setting, access needs and intended result. Check these against the stated limits. Use the supplied rules and materials. Explain any proposed changes before using them, and label them as adaptations. Do not invent source claims or require personal disclosure. Give me one step at a time when I say start. I manage the people, physical activity and clock; do not claim to observe the room. Ask me what happened before choosing a next step.

Reference revision: 6687436a35fa6842a07008f3dac25d23d17f4af16b3d4589bb5e4cc1ad264aef

# Sprint Retrospective: 4 Ls Framework

Team members record individual observations across four categories (Liked, Learned, Lacked, Longed For) and jointly decide on concrete workflow adjustments for the next cycle.

**Time:** 45 minutes. UWT suggested standard 45-minute sprint cadence based on guidance in the source article.
**People:** 4 to 16. Individual silent reflection, whole-group clustering and prioritization, followed by volunteer or pair commitments.

## Choose this exercise

**Purpose:** Produce a prioritized list of specific process improvements for the next sprint with clear ownership or shared commitments.
**Use it when:** At the conclusion of a work cycle or sprint when a team needs to review its process and agree on practical adjustments.
**Skip it when:** When the team faces unresolved interpersonal conflict requiring mediation, or when the team lacks authority to modify its workflow.

## Materials and tools

- 1 pad of sticky notes per participant
- 1 fine-tip marker per participant
- 1 large whiteboard or wall space divided into 4 columns (Liked, Learned, Lacked, Longed For)
- Timer

## Before participants arrive

1. Draw four equal columns on a whiteboard labeled: Liked, Learned, Lacked, and Longed For.
2. Distribute sticky notes and markers to each seat.
3. Ensure everyone has direct line of sight to the board.

## Say this to open

Welcome to our sprint retrospective. Our goal is to examine our workflow from start to finish, spot what supported us, identify friction, and choose concrete changes for our next sprint. We will use four categories: Liked, Learned, Lacked, and Longed For. Focus on processes, tools, and communication patterns. Criticism must remain constructive, respectful, and free of personal blame. You may pass on speaking during open sharing if your notes already express your view.

## How to run it

### 1. Introduce columns and prompt silent writing (8 minutes)

Explain the four categories using the opening script. Direct everyone to write individual notes silently. Aim for one clear idea per sticky note across any category. Neutral example: under Lacked, write 'access to staging server on day two' rather than 'ops team was slow'. Writing stops when the timer chimes.

### 2. Post and group notes (12 minutes)

Invite participants to walk up and place their notes in the corresponding column. Group related items into thematic clusters as they are posted. Once notes are up, read each cluster aloud quickly without debating solutions.

### 3. Identify patterns and prioritize themes (10 minutes)

Ask the room to review the clusters, particularly under Lacked and Longed For. Give each person three dot votes (or marker checkmarks) to place on the issues most critical to address in the upcoming sprint. Count votes to highlight the top two or three priorities.

### 4. Formulate actionable improvements and assign owners (10 minutes)

Take the top two or three clusters. Prompt the room: 'What specific, realistic action will we take next sprint to resolve this?' Record each concrete task on the board. Ask for individual volunteers to own each item. If an item feels too large for one person, invite a pair to share responsibility. If no volunteer steps forward for an item, confirm whether the team will carry it as a shared team checklist agreement or table it for a later cycle. Do not mandate an unwilling owner.

### 5. Debrief and close (5 minutes)

Review the recorded action commitments and verify target dates. Pick one or two debrief questions and take two to three brief whole-room responses to fit the remaining time.


## Debrief questions

- Which action item will make the most immediate difference in our next sprint?
- Did our review highlight any shared bottlenecks that were previously hidden?
- How realistic is the workload of the commitments we just recorded?

**Finished output:** A documented list of two to three specific process adjustments for the upcoming sprint, recorded with an individual volunteer, volunteer pair, or explicit whole-team agreement.

## Remote

Set up a digital board with four columns (Liked, Learned, Lacked, Longed For). Participants create digital sticky notes during the silent writing phase. The facilitator reads items aloud and drags them into thematic clusters. Use built-in voting features or reaction stamps for the 3-vote prioritization step.

## Hybrid

All participants, whether in-room or remote, use the shared digital board from their personal devices. An in-room screen displays the board for shared view. Verbal contributions alternate strictly between in-room and remote speakers.

## Access and participation choices

- Participants may post notes without reading them aloud.
- Anyone may choose to pass on speaking or volunteering for action items.
- Digital boards must support screen magnification and high-contrast settings.

## If the session gets stuck

**Discussion turns into personal venting or finger-pointing.**

Intervene immediately and redirect the speaker: reframe the criticism from individual personality to system, tool, or communication process.

**Team generates too many action items to realistically execute.**

Enforce a strict cap of three action items total. Park remaining suggestions in an improvement backlog for future retrospectives.


## Terms used here

- Sprint: A short, fixed period of time during which a team completes a set amount of work.
- 4 Ls: A retrospective structure reviewing what the team Liked, Learned, Lacked, and Longed For.

## Sources and adaptation

Observed in EasyRetro guide 'How To Run A Sprint Retrospective' (easyretro.io), which details sprint debrief practices and the 4 Ls retrospective format.

The source guide outlines broad retrospective advice and highlights the '4 Ls' framework as a core structured feedback tool. UWT organized this into a timed 45-minute facilitator run sheet with explicit steps for silent writing, thematic clustering, dot voting, and volunteer or pair action commitments.

[EasyRetro](https://easyretro.io/sprint-retrospective/how-to-run-a-sprint-retrospective)

[EasyRetro](https://easyretro.io/sprint-retrospective/how-to-run-a-sprint-retrospective/)

Current run sheet: https://unitedwetransform.com/exercises/how-to-run-a-sprint-retrospective/