Random Retrospective Generator

Choose this exercise

Purpose: Select an unfamiliar retrospective framework at random to review work patterns from a fresh angle.

Use it when: Use when a team is bored with standard retro formats and needs a structured way to vary their reflection prompt.

Skip it when: Skip when the team has experienced a critical operational incident that requires a rigorous timeline or root-cause post-mortem.

Group arrangement: Whole group for 8 or fewer; parallel breakout subgroups of 4 to 6 for 9 to 24 participants

Timing: UWT suggested duration for a complete 45-minute retrospective session

Materials and tools

• 1 standard six-sided die (or a 1 to 6 digital number generator)
• Sticky notes (1 pad per participant)
• Felt markers (1 per participant)
• Whiteboard or wall space with painter tape to create columns
• 1 copy of the Retrospective Format Menu

Before participants arrive

1. Post the 6 template options from the Retrospective Format Menu where all participants can see them.
2. Distribute sticky notes and markers to each seat.

Say this to open

To avoid running the exact same retrospective every cycle, we will roll a die to choose our framework for today. Whatever number comes up, we will set up those specific reflection categories and review our last cycle using that lens.

How to run it

1. Roll and set columns 5 minutes

   One participant rolls the six-sided die. Match the number to the Retrospective Format Menu. The facilitator draws the corresponding categories as columns across the board. The opening script happens during this step.

2. Individual silent ideation 10 minutes

   Participants write one observation per sticky note under any of the selected columns. Silence is maintained. People may write as many notes as they wish or choose to submit none.

3. Cluster and review notes 15 minutes

   Participants post their notes in the designated columns. In groups of 8 or fewer, each person presents their notes aloud in 60 seconds while the room groups related topics. In groups of 9 or more, split into breakout groups of 4 to 6 to read and cluster common topics. Stop when clusters are grouped.

4. Agree on concrete actions 15 minutes

   The group selects up to 2 specific, observable changes to implement in the next working cycle. Each chosen action must have a named owner and a deadline. Record these items publicly.

Debrief questions

• How did this framework highlight things that our usual review questions miss?
• Which action item should we check first in our next cycle?

Finished output: A board of categorized reflection notes and a written list of 1 to 2 agreed next actions with designated owners.

Remote

Use a shared digital whiteboard pre-configured with the 6 menu options. A participant rolls a virtual die using an online generator or chat command. The facilitator opens the matching column template. Participants have 10 minutes to add digital sticky notes silently. For step 3, use breakout rooms if over 8 participants, or run a whole-room order where each person reads one note at a time while the facilitator or speaker moves sticky notes into visible thematic clusters. For step 4, use digital dot voting (2 votes per person) to pick the top 2 clusters, then agree aloud on one owner and deadline for each.

Hybrid

Run the entire session on a single shared digital whiteboard visible on the room screen and on remote laptops. A remote participant triggers a digital die roll shared on screen. In-person and remote participants both post directly to the digital board from their laptops or phones. During clustering, alternate speaking turns between in-room and remote speakers, moving cards on the shared screen so all participants see the same clusters. For action selection, everyone casts 2 votes directly on the digital board, and the group discusses assignments over the combined room audio.

Access and participation choices

• Participants may submit notes anonymously or pass on speaking aloud during the clustering review.
• Clear printed column labels help participants with visual or processing differences follow the chosen framework.

If the session gets stuck

The die lands on a template the team used at the very last meeting.

Reroll once to ensure variety, or offer the team a quick vote on whether to reroll.

Participants write vague complaints without actionable details.

Ask the author: 'What observable behavior or process change would fix this next week?'

Terms used here

• Sprint Retrospective: A recurring meeting where a project team reflects on their recent cycle to improve processes.