# Relentless Improvement Retrospective

Teams evaluate an iteration across five columns, sort pain points by direct team control, and translate their top internal friction into owned backlog action items.

**Time:** 50 minutes. EasyRetro suggests 30 to 60 minutes. Set to 50 minutes to accommodate clustering, control filtering, and actionable problem solving for up to 16 people.
**People:** 4 to 16. Individual reflection, followed by whole-group triage, voting, and paired or whole-group action planning.

## Choose this exercise

**Purpose:** Identify team friction points within direct control and convert them into owned backlog action items for the upcoming iteration.
**Use it when:** At the conclusion of a delivery iteration or milestone when transitioning from numeric metrics to team workflow refinements.
**Skip it when:** When conducting an urgent production incident post-mortem or when the team lacks mandate to alter its own workflow practices.

## Materials and tools

- Whiteboard or digital board configured with 5 main columns (Kudos, Happy With, Not Happy With, To Improve, Action Items) plus an External Dependencies holding box
- Sticky notes (5 pads of 100 sheets each)
- Fine-tip markers (1 per person)
- Dot stickers for voting (3 dots per person)

## Before participants arrive

1. Draw or build 5 columns on the board: 'Thank you / Kudos', 'I am happy with', 'I am not happy with', 'To improve', and 'Action Items'.
2. Draw a distinct box labeled 'External Dependencies' below or beside the main board.
3. Distribute sticky pads and markers, or confirm digital board edit access for all participants.

## Say this to open

Welcome to our retrospective. We will evaluate our recent work across five columns, moving from left to right. Our primary goal is to identify our biggest friction points, filter for what is within our direct team control, and commit to one or two concrete backlog actions for next iteration. Critique systems and workflows, not individuals.

## How to run it

### 1. Introduce columns and boundaries (3 minutes)

Read the opening script. Review the board layout and explain the ground rule: critique processes and tooling, not personalities. Point out the External Dependencies parking box.

### 2. Generate reflections silently (7 minutes)

Participants write notes silently and post them under the first three columns: 'Thank you / Kudos', 'I am happy with', and 'I am not happy with'. One clear observation per note. People may post as many as needed or pass.

### 3. Cluster and filter by control (18 minutes)

Facilitator briefly reads aloud the Kudos and Happy With cards. Then move to 'I am not happy with'. Group related complaint cards together. For each cluster, ask: 'Can this team solve this directly, or does it sit outside our control?' If outside our control, physically move those cards into the External Dependencies box. Leave only actionable, internally solvable pains in the column.

### 4. Vote on priority pains (4 minutes)

Distribute 3 voting dots to each participant. Participants place dots on the internally solvable pain points they believe need the most urgent resolution in the next iteration. Count the dots and identify the top 1 or 2 items.

### 5. Formulate owned actions (13 minutes)

Move the top 1 or 2 chosen issues into 'To improve'. As a group, draft specific, measurable counter-measures. Transfer the resulting concrete tasks into 'Action Items'. Assign exactly one named team member as the owner for each task.

### 6. Confirm commitments and wrap up (5 minutes)

Ask 1 or 2 debrief questions to the group. Confirm that the assigned task owners will enter their action items directly into the team backlog before the next planning session. Confirm who routes external dependency notes to relevant partners.


## Debrief questions

- Which improvement item will have the most direct impact on our next iteration?
- What is one practice from 'Happy with' that we must protect during busy periods?
- Who will deliver the notes parked under External Dependencies to leadership or partner teams?

**Finished output:** One or two actionable improvement cards assigned to single team owners and added to the official team backlog, plus an optional parking list of external dependencies.

## Remote

Set up a shared digital whiteboard with the five columns and an external holding area. Run a visible timer during writing. Triage notes systematically by column. Use digital dot stamps for voting. Manage spoken turns using the platform hand-raise queue.

## Hybrid

All participants use a single digital board. In-person participants type on their own devices or write notes transcribed immediately by an in-room scribe. The facilitator mirrors screen shares and monitors the digital chat queue.

## Access and participation choices

- Participants may submit items silently or pass on writing in any column.
- Contributions can be written anonymously on sticky notes or digital cards.
- Items flagged as outside team control are acknowledged without demanding personal justification.

## If the session gets stuck

**Participants dwell on issues caused entirely by outside teams or executive policy.**

Intervene and move the card immediately to the External Dependencies box. Remind the room that retrospectives only solve what this specific team can change tomorrow.

**Action items are drafted as vague aspirations like 'improve test coverage'.**

Require an explicit definition of done: 'What specific checklist item, meeting change, or task will show this was completed during next iteration?'


## Terms used here

- Backlog: A prioritized inventory of tasks, fixes, and process enhancements scheduled for future work.
- Iteration: A timeboxed cycle during which a team completes a set portion of work.

## Sources and adaptation

Observed in EasyRetro template collection, attributed to Amatus Saboor Husain.

Retained the five columns from the EasyRetro source (Thank you / Kudos, I am happy with, I am not happy with, To improve, Action Items) and the control filter mechanic. Expanded the overall timebox to 50 minutes to allow adequate discussion during clustering, sphere-of-control filtering, and action commitment. Specified an explicit External Dependencies holding area for out-of-control items.

[EasyRetro](https://easyretro.io/templates/relentless-improvement/)

Current run sheet: https://unitedwetransform.com/exercises/relentless-improvement/