Weather Forecast Retrospective

Choose this exercise

Purpose: Catalog team challenges and wins from a recent iteration using four weather metaphors to agree on process improvements.

Use it when: At the end of a sprint or milestone when a team needs a straightforward mood check and practical process review.

Skip it when: When conducting a formal incident post-mortem that requires a strict chronological timeline and deep technical failure analysis.

Group arrangement: Individual drafting, paired cluster review in tables, and whole-group synthesis.

Timing: UWT suggested duration for groups up to 24, scaled from source template categories.

Materials and tools

• Sticky notes (2 pads per table of 4 to 6 people)
• Dark fine-tip markers (1 per participant)
• Whiteboard or wall space divided into 4 columns: Stormy, Rainy, Cloudy, Sunny
• Countdown timer visible to the room

Before participants arrive

1. Draw four vertical columns across a wide whiteboard or wall.
2. Label the columns from left to right: Stormy, Rainy, Cloudy, Sunny.
3. Place sticky note pads and markers on every table.

Say this to open

Welcome to our retrospective. Today we are using a weather forecast to assess our recent work cycle. We have four columns: Stormy for severe breakdowns, Rainy for ongoing hurdles, Cloudy for mixed results, and Sunny for clear wins. Please write your thoughts silently, one observation per sticky note.

How to run it

1. Explain categories and write notes 8 minutes

   Distribute the reference definitions. Ask everyone to write silently on sticky notes, aiming for 2 to 4 notes total across any categories they choose. Example: 'Nightly build failed three times' belongs in Rainy; 'Demo to client ran smoothly' belongs in Sunny. Silence allows everyone space to reflect.

2. Post and cluster in small groups 14 minutes

   For groups up to 8, participants post directly to the wall. For larger groups, tables spend 5 minutes grouping their own notes, then designated table runners place clustered themes on the main board. The facilitator reads major clusters aloud, merging clear duplicates across tables with brief verbal checks.

3. Analyze patterns and discuss causes 18 minutes

   Look at the balance across the board. If Stormy or Rainy clusters dominate, prompt the room to identify the primary root causes. If Cloudy clusters dominate, ask what specific changes would remove the uncertainty. If Sunny dominates, identify which specific practices the team should standardize. Take up to 4 comments per major theme.

4. Select and assign action items 10 minutes

   Invite the team to propose 2 or 3 realistic changes to address the largest issues identified. Vote by a quick show of hands if proposals conflict. For each selected item, assign a single owner and an exact target date. Write these items in a distinct Action Items box on the board.

Debrief questions

• Which pattern or concentration of notes was most unexpected?
• What is one concrete fix from the Rainy or Stormy columns that will remove friction fastest?
• What practice highlighted under Sunny should become our team standard?

Finished output: A board of clustered feedback notes under four weather categories and two to three assigned action items with owners and deadlines.

Remote

Use an online board with columns for Stormy, Rainy, Cloudy, and Sunny. Participants write cards silently during the first step. In breakout rooms or all together, participants use board voting or drag-and-drop grouping to cluster cards before the facilitator facilitates voice discussion.

Hybrid

Maintain a primary shared digital board. In-person participants type directly into laptops or pair with a designated scribe who mirrors physical sticky notes onto the digital board in real time during the posting step. Share the digital board on the physical room screen so all participants view the identical layout simultaneously.

Access and participation choices

• Participants may submit notes anonymously without initials.
• Anyone may choose to submit notes in only one category or pass on verbal discussion.
• Written chat or physical notes are accepted equally.

If the session gets stuck

One vocal participant dominates the open discussion.

Acknowledge the point, note it on the board, and invite input specifically from someone at another table who has not spoken.

Notes are vague complaints without actionable details.

Ask the room or note writer for a specific recent example of that friction to reveal the operational issue.

Terms used here

• Retrospective: A structured team meeting at the close of an iteration to inspect how the team worked and identify changes.
• Sprint: A short, fixed time box in which a team completes a set amount of work.