# The Matrix Retrospective

Participants categorize sprint observations into four themed columns: System Glitches, System Strengths, Code Patches, and Next Launch. They cluster common themes and dot-vote to select up to three owned action experiments.

**Time:** 15 minutes. 15 minutes matches the source template for co-located or remote teams of up to 12 participants.
**People:** 4 to 12. Individual silent reflection followed by whole-room clustering and dot-voting.

## Choose this exercise

**Purpose:** Identify process bugs, capture existing workarounds, and establish owned action items for the upcoming cycle.
**Use it when:** Use at the end of a sprint or project milestone, particularly with technical or software delivery teams that enjoy computing or sci-fi themes.
**Skip it when:** Skip when the team dislikes metaphor-heavy reviews, when resolving sensitive interpersonal conflict, or when reviewing broad organizational strategy.

## Materials and tools

- Whiteboard or wall space divided into four columns
- Sticky notes (one pad per participant)
- Fine-tip markers (one per participant)
- Sticky dot stickers (3 dots per participant)

## Before participants arrive

1. Draw four columns on the board labeled: 'System Glitches (What broke or blocked us)', 'System Strengths (What ran well)', 'Code Patches (Fixes we already made)', and 'Next Launch (Experiments to try next)'.
2. Distribute sticky notes, a marker, and a strip of 3 dot stickers to each participant workstation.

## Say this to open

We are running a 15-minute retrospective using four system-themed columns: System Glitches, System Strengths, Code Patches, and Next Launch. Take three minutes in silence to write your observations on sticky notes, one thought per note, and place them into the matching columns.

## How to run it

### 1. Introduce and write cards (3 minutes)

Read the opening script aloud. Participants write observations silently on sticky notes. For example, a note in System Glitches could be 'CI build queue exceeded 40 minutes', while Code Patches could be 'Ran local unit tests before committing to bypass the queue'. Anyone may write multiple cards, single cards, or choose to observe silently without writing.

### 2. Post and cluster cards (4 minutes)

Participants walk up and post their notes under the matching columns. The facilitator reads notes aloud quickly and merges exact duplicates or directly related topics into visible clusters. Avoid opening deep debates during this phase.

### 3. Dot-vote and prioritize next launch (5 minutes)

Direct attention to the Next Launch column and any high-impact Glitches that need an immediate fix. Each participant places their 3 dot stickers on the ideas they believe should be tackled first. The facilitator reads the top 1 to 3 vote-getters and asks for a volunteer owner for each item.

### 4. Review actions and wrap up (3 minutes)

Read the 1 to 3 selected experiments and confirmed volunteer owners aloud. Ask one debrief question from the list to conclude the session within the remaining time.


## Debrief questions

- Which Next Launch experiment will remove our biggest current glitch?
- Are there any Code Patches from this sprint that we should adopt as permanent team standards?

**Finished output:** A four-column review board with clustered cards and one to three documented Next Launch action items with named volunteer owners.

## Remote

Use an online whiteboard configured with the four labeled columns. Participants type notes directly onto digital sticky notes during silent writing. In step 2, the facilitator shares the screen and clusters similar cards. In step 3, participants use digital dot stamps or reaction emojis (limit 3 per person) to vote on Next Launch items. Record the top items and volunteer owners in the meeting chat.

## Hybrid

All participants, whether remote or in-person, contribute directly to the shared digital whiteboard via laptops. Display the digital board on the physical room screen with an open shared microphone. In-person participants without laptops pair with an in-room scribe or pass written notes to be transcribed onto the digital board.

## Access and participation choices

- Participants may submit cards anonymously or privately message items to the facilitator to post.
- Participants can pass on writing notes, voting, or speaking without giving a reason.
- Ensure high-contrast, legible text labels for all four columns rather than relying solely on color codes or decorative graphics.

## If the session gets stuck

**Participants spend all their energy venting under System Glitches and ignore constructive fixes.**

Enforce the timer strictly. Acknowledge the glitch, cluster it, and immediately ask what practical experiment in Next Launch would prevent it.

**Proposed Next Launch ideas are vague aspirations like 'communicate better'.**

Ask the group for a concrete test: 'What specific trigger or checklist item will we test starting Monday morning?'


## Terms used here

- Code Patches: Temporary adjustments, workarounds, or interim fixes the team implemented during the cycle.
- Next Launch: Concrete experiments, operational adjustments, or process trials targeted for the upcoming cycle.

## Sources and adaptation

Observed on EasyRetro as a community template attributed to Bogdan, drawing upon cyberpunk and Matrix computer terminology.

Retained the four Matrix-themed retrospective categories and the original 15-minute timeframe from the EasyRetro community template by Bogdan. Capped group size at 12 to ensure whole-group clustering and dot-voting fit strictly within 15 minutes. Integrated explicit dot-voting mechanics to resolve prioritization clearly without stalling.

[EasyRetro](https://easyretro.io/templates/the-matrix-retrospective/)

Current run sheet: https://unitedwetransform.com/exercises/the-matrix-retrospective/