Field guideTeam Retro Guide

Facilitator guide

Team Retrospective Facilitator Guide

A practical guide to reviewing work, learning together and agreeing on useful next steps.

120minutes · 6 sessions

For
Team leads and facilitators running a retrospective with a project or delivery team
Length
2 h
Format
Self-paced
Prepared by
Mara Ellison (fictional)

000 / Contents6 sessions

  1. 01Warm-up: arrive and check inWarm-up · 1 step0:00–0:10
  2. 02Agenda and working agreementsConcept · 1 step0:10–0:20
  3. 03Activity: map the workPractice · 1 step0:20–0:45
  4. 04Activity: find patternsPractice · 1 step0:45–1:10
  5. 05Activity: design an experimentPractice · 1 step1:10–1:35
  6. 06Closing: assign and confirm actionsDebrief · 1 step1:35–2:00

Before you begin

You will leave with

  • Set clear ground rules for a constructive retrospective.
  • Help a team identify events and patterns that affected its work.
  • Guide the team from observations to a small, testable improvement.
  • Record action items with an owner, measure and review date.

01 / Warm-up0:00–0:10

Warm-up: arrive and check in

Help each person settle in and share a brief, work-focused check-in.

10 min1 stepActivity: 10 min
1.1

One-word check-in

Try it · 10 min

Invite a short check-in without asking anyone to explain more than they wish.

  • Help everyone contribute early.
  • Set a calm, non-judgmental tone.

Ask each person to name one word or short phrase for how they are arriving. Passing is allowed. Keep this separate from evaluating the work; the goal is to hear the room, not to solve anything yet.

Run the check-in

  1. 1
    Frame the prompt

    Say that people may share a word, a phrase or pass.

  2. 2
    Invite a round

    Give each person a turn without cross-talk or follow-up questions.

  3. 3
    Name what you heard

    Briefly reflect the range of energy in the room without interpreting anyone's response.

Saved in this browser only. Nothing is sent anywhere.

02 / Concept0:10–0:20

Agenda and working agreements

Make the purpose, sequence and participation agreements visible.

10 min1 step
2.1

Set the frame

Read · 10 min

Explain the flow and agree how the team will discuss difficult moments.

  • Describe the purpose of each part of the session.
  • Agree on behaviors that support open discussion.

State the work period being reviewed and the question the team wants to answer. Explain that the group will map events, examine what helped or hindered, choose one experiment and assign follow-through. The aim is learning and improvement, not a verdict on individual performance.

Make the agenda usable

  1. 1
    Name the scope

    Write the project, sprint or date range where everyone can see it.

  2. 2
    Explain the sequence

    Preview the warm-up, three activities and closing action review.

  3. 3
    Agree on behaviors

    Ask the group to listen to understand, speak from direct experience and challenge ideas without attacking people.

  4. 4
    Choose a parking area

    Record topics that matter but do not fit the current scope, then identify who will revisit them.

Checklist

Before moving on

03 / Practice0:20–0:45

Activity: map the work

Create a shared, fact-based view of significant events and transitions.

25 min1 stepActivity: 25 min
3.1

Build an event timeline

Try it · 25 min

Collect observations independently, then arrange them in sequence.

  • Record specific events from the selected work period.
  • Distinguish observable events from interpretations.

A timeline helps the team compare what people experienced before drawing conclusions. Ask for concrete events: a handoff, a changed requirement, a release, a delay or a decision. Keep each note focused on one event and add an approximate date or phase when possible.

Create the timeline

  1. 1
    Set the boundaries

    Mark the start and end of the work period on a board.

  2. 2
    Write silently

    Ask everyone to add individual notes for significant events. One event per note; use neutral wording.

  3. 3
    Place notes in sequence

    Invite the group to position notes by date or project phase. Ask for clarification where accounts differ.

  4. 4
    Mark turning points

    Let participants mark events they believe changed the direction, pace or quality of the work.

WriteRecord an event, when it happened and what changed as a result.

Saved in this browser only. Nothing is sent anywhere.

04 / Practice0:45–1:10

Activity: find patterns

Examine what supported progress and what created friction.

25 min1 stepActivity: 25 min
4.1

Sort conditions and effects

Try it · 25 min

Group timeline observations into useful themes without turning them into personal judgments.

  • Identify conditions that helped or hindered the work.
  • Support a pattern with specific observations.

Use the timeline as evidence. Look for repeated conditions, such as unclear decision ownership, late feedback or a dependable handoff. A pattern is more useful than a complaint when the team can point to examples and describe its effect on the work.

Look for patterns

  1. 1
    Choose observations

    Select timeline notes that seem connected. Keep the original notes visible.

  2. 2
    Name a condition

    Describe the working condition in neutral terms, such as 'review requests arrived after implementation.'

  3. 3
    Trace the effect

    Ask what the condition made easier or harder, and who or what was affected.

  4. 4
    Check the pattern

    Ask for another example or a different perspective before treating the theme as shared.

Sort it

Place each observation under the effect it best describes. If its effect is unclear, discuss it before sorting.

  1. A named reviewer responded before work moved to the next stage.
  2. A requirement changed after the team had completed implementation.
  3. The same people joined a planning discussion and a delivery handoff.
  4. A blocked task had no visible owner for the next update.

WriteCapture a pattern and the evidence that supports it.

Saved in this browser only. Nothing is sent anywhere.

05 / Practice1:10–1:35

Activity: design an experiment

Turn a priority pattern into a small, testable change.

25 min1 stepActivity: 25 min
5.1

Choose a change to test

Try it · 25 min

Define a practical experiment, a signal of success and a review point.

  • Write an experiment that addresses a selected pattern.
  • Choose a signal the team can observe during the next work period.

Prefer a small change the team can try without waiting for a major reorganization. Make the link explicit: the pattern is the condition, the experiment changes one part of that condition, and the signal shows whether the change helped. If the team cannot influence a condition, name the person or group who can.

Design the experiment

  1. 1
    Select one pattern

    Choose a pattern the team can influence and that has a meaningful effect on the work.

  2. 2
    State the change

    Write what the team will do differently, where it applies and when it begins.

  3. 3
    Choose a signal

    Pick an observable measure or event, such as fewer handoffs returned for missing information.

  4. 4
    Set a review point

    Choose when the team will check the signal and decide whether to keep, adapt or stop the experiment.

Knowledge checkWhich experiment statement is easiest to learn from?

06 / Debrief1:35–2:00

Closing: assign and confirm actions

Turn the experiment into owned next steps and close with a clear handoff.

25 min1 step
6.1

Record commitments and close

Reflect · 25 min

Assign an owner, a next step and a review point for each agreed action.

  • Record actions with clear ownership and follow-up.
  • Check that participants understand what happens next.

An action item needs one accountable owner, a concrete next step and a date or event for review. The owner coordinates the action; that does not mean they must do every task alone. Keep the experiment visible and decide where the team will revisit its evidence.

Close the loop

  1. 1
    Read back the experiment

    Confirm the change, the signal and the review point with the group.

  2. 2
    Assign ownership

    Name one owner for each action and ask them to confirm the next step.

  3. 3
    Make follow-up visible

    Record where the action and review date will be tracked.

  4. 4
    Invite a final reflection

    Ask each person for one useful observation or one word about the session; passing is fine.

WriteRecord the agreed actions and review point.

Saved in this browser only. Nothing is sent anywhere.

Checklist

Before the group leaves

End / Your notesEverything you wrote, in one place

  1. 1.1 One-word check-in

    What do you want the group to keep in mind about how you are arriving?

  2. 1.1 One-word check-in

    What would help you take part honestly and constructively today?

  3. 2.1 Set the frame

    Write the scope and the question this retrospective should answer.

  4. 3.1 Build an event timeline

    Record an event, when it happened and what changed as a result.

  5. 3.1 Build an event timeline

    Which event do you think the group should understand better before deciding what to change?

  6. 4.1 Sort conditions and effects

    Capture a pattern and the evidence that supports it.

  7. 4.1 Sort conditions and effects

    Which pattern is most important to address, and what evidence makes it worth attention?

  8. 5.1 Choose a change to test

    Complete the experiment: We will change… We expect… We will notice it helped if… We will review it when…

  9. 6.1 Record commitments and close

    Record the agreed actions and review point.

  10. 6.1 Record commitments and close

    What is one thing you will do to support the agreed experiment?

Notes stay in this browser only. Nothing is sent anywhere.