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: f525ca59de82a92fa915c17f4eb77cf968b74eb2d4611c454de419d6afab1abf

# Project Retrospective Template

Team members write reflections under three columns: What Worked, What Needs Improvements, and Actions. They celebrate successes first, examine process friction without blaming individuals, and define concrete next steps with named owners.

**Time:** 45 minutes. UWT suggested running time for a thorough 3-column project debrief. Evidence notes easy execution with no group limit.
**People:** 4 to 24. Individual silent generation followed by trios and whole-group consolidation.

## Choose this exercise

**Purpose:** Document project successes, process gaps, and clear action items for future initiatives.
**Use it when:** At the close of a project, release, or milestone to assess delivery and build operational changes.
**Skip it when:** During an ongoing mid-cycle emergency or when interpersonal conflict requires mediated dispute resolution rather than process evaluation.

## Materials and tools

- 1 physical whiteboard or clear wall section labeled with three columns: What worked?, What needs improvements?, and Actions
- 1 pad of sticky notes per participant
- 1 felt-tip marker per participant
- 1 countdown timer
- Digital whiteboard link for remote or hybrid delivery

## Before participants arrive

1. Draw three distinct vertical columns on the board labeled: 'What worked?', 'What needs improvements?', and 'Actions'.
2. Place sticky notes and markers at each seat.
3. If running hybrid, prepare the digital whiteboard columns and ensure meeting audio captures the room.

## Say this to open

Welcome to our project retrospective. Our goal today is to evaluate how this project went and decide what we will carry into our next project. We will use three categories: What worked, What needs improvements, and Actions. We start with successes to celebrate contributions, then inspect friction without pointing fingers, and finish with concrete action items. Writing is individual and you choose what you share.

## How to run it

### 1. Introduce scope and ground rules (5 minutes)

State the project dates and milestones under review. Share the opening script. Emphasize the core ground rule: critique processes and tools, not individual people. Clarify that anyone may pass or decline to share specific notes.

### 2. Silent generation on successes and challenges (10 minutes)

Direct participants to write one clear idea per sticky note. Use 'What worked?' for successes, acknowledgments, and effective tools. Use 'What needs improvements?' for external roadblocks, communication gaps, or task shortfalls. Example: 'Automated test suite caught two release blockers' under What worked; 'Client approval window was too short for QA' under What needs improvements. Participants work quietly.

### 3. Small-group clustering (10 minutes)

Form groups of 3 (or 4 if numbers require). Trios walk to the board, post their notes into the first two columns, read their cards aloud briefly, and cluster duplicate topics together under shared themes.

### 4. Identify actions (12 minutes)

Bring the whole group together facing the board. Review the main clusters in 'What needs improvements'. Ask each trio from the previous step to draft 1 or 2 concrete proposal cards for the 'Actions' column addressing these clusters. Each action note must include an observable task, an agreed owner, and a target date.

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

Review the posted Actions column with the whole room. Confirm each action has an agreed owner. Ask 2 or 3 volunteers to answer the debrief questions.


## Debrief questions

- Which action on the board will make the most immediate difference in our next launch?
- What positive practice from this project should become a standard working rule for every future project?

**Finished output:** A shared board displaying categorized retrospective notes and an agreed list of assigned action items.

## Remote

Set up a shared digital whiteboard with three labeled columns: What worked, What needs improvements, Actions. Run the silent generation individually on the board. Move participants into breakout rooms of 3 for clustering. Reassemble in the main room to draft and assign actions.

## Hybrid

Maintain a single digital whiteboard as the primary source of truth. Have on-site participants bring laptops or pair each remote participant with an on-site partner who mirrors notes to the digital board. For the clustering step, create mixed breakout groups using laptop video or keep all remote participants in one breakout room while physical participants group in the room. Both groups cluster cards on the shared digital board simultaneously.

## Access and participation choices

- Participants may post written cards directly without speaking aloud.
- Any participant may pass on writing or speaking during any round without justification.

## If the session gets stuck

**Participants post blame directed at a specific colleague under 'What needs improvements'.**

Intervene immediately and rephrase the card into a system or workflow issue. For example, change 'Person X missed the deadline' to 'Handoff timelines lacked explicit buffer days'.

**The Actions column produces vague goals like 'Communicate better'.**

Ask the group: 'What specific artifact or calendar event creates that communication?' Update the note to an observable task like 'Add a 10-minute daily sync during launch week'.


## Terms used here

- Retrospective: A structured team meeting to review a completed body of work and identify adjustments for future cycles.

## Sources and adaptation

Observed in EasyRetro template repository, created by Tchales Jr. and noted as inspired by fellow.app.

Retained the three core columns (What worked, What needs improvements, Actions) and core guidance from Tchales Jr. / EasyRetro. UWT structured the 45-minute progression, clarified subgroup clustering to avoid contradictory pair instructions, added specific hybrid participation rules, and standardized the blame-free framing.

[EasyRetro](https://easyretro.io/templates/project-retrospective-template/)

Current run sheet: https://unitedwetransform.com/exercises/project/