Field guideTeam Retrospective

FACILITATOR GUIDE

Facilitator Field Guide: Team Retrospective

A practical guide to reviewing recent work and choosing useful next steps

120minutes · 6 sessions

For
Facilitators and team leads guiding a team through a retrospective
Length
2 h
Format
Self-paced
Prepared by
Maya Chen (fictional)

000 / Contents6 sessions

  1. 01Arrive and focusWarm-up · 1 step0:00–0:10
  2. 02Make participation workableConcept · 1 step0:10–0:25
  3. 03Gather observationsPractice · 1 step0:25–0:50
  4. 04Find patterns and meaningPractice · 1 step0:50–1:20
  5. 05Choose a small experimentPractice · 1 step1:20–1:45
  6. 06Close and carry learning forwardDebrief · 1 step1:45–2:00

Before you begin

You will leave with

  • Set clear participation and confidentiality agreements
  • Gather observations without blame
  • Identify patterns and explore their causes
  • Turn insights into specific, owned actions

01 / Warm-up0:00–0:10

Arrive and focus

Help the team settle in and agree on what they are reviewing.

10 min1 stepActivity: 10 min
1.1

Settle in and choose a focus

Try it · 10 min

Create a shared starting point for the conversation.

  • Name the work period or event under review

Welcome everyone. Name the work being reviewed and its boundaries, such as a release, a project phase, or the past few weeks. Keep the focus on how the work went, not on judging individuals.

Open the session

  1. 1
    Name the focus

    State the work period and why the team is reviewing it.

  2. 2
    Invite a quick check-in

    Ask each person for one word describing how they arrive today.

  3. 3
    Set a shared aim

    Ask what would make this conversation useful. Capture a short answer.

02 / Concept0:10–0:25

Make participation workable

Agree on conditions that support honest, balanced discussion.

15 min1 stepActivity: 15 min
2.1

Agree how to work together

Try it · 15 min

Set practical norms before sharing observations.

  • Agree on simple norms for participation

A useful retrospective makes room for different perspectives. Ask the group to agree on a few behaviors that will help people speak and listen openly. Do not promise absolute confidentiality if the team cannot guarantee it; agree instead on what may be shared outside the room.

Build working agreements

  1. 1
    Offer a starting point

    Suggest listening without interruption, speaking from personal experience, and questioning processes rather than motives.

  2. 2
    Invite additions

    Ask what else people need in order to take part honestly.

  3. 3
    Confirm boundaries

    Agree what notes may be shared and what should stay within the group.

Checklist

Agreements to consider

03 / Practice0:25–0:50

Gather observations

Collect concrete examples of what helped and hindered the work.

25 min1 stepActivity: 25 min
3.1

Build a shared picture

Try it · 25 min

Give everyone quiet time to contribute before discussion begins.

  • Record specific observations from the work period

Start with observations, not explanations. Encourage examples tied to a moment, decision, handoff, or outcome. Silent writing first reduces the chance that the first speaker sets the direction for everyone else.

Collect observations

  1. 1
    Write silently

    Ask each person to note what helped the work and what made it harder. Use one idea per note.

  2. 2
    Make examples concrete

    Invite details such as what happened, when it happened, and what effect it had.

  3. 3
    Share in turns

    Give each person a chance to post or read notes without debate.

  4. 4
    Group related notes

    Place similar observations together while preserving differences that matter.

WriteWhat helped the work? What made it harder?

HelpedMade it harder

04 / Practice0:50–1:20

Find patterns and meaning

Explore what the observations may reveal about the team's way of working.

30 min1 stepActivity: 30 min
4.1

Explore themes without jumping to blame

Try it · 30 min

Look for recurring conditions and test interpretations against examples.

  • Identify a pattern supported by multiple observations

A cluster of notes may point to a recurring condition, such as unclear ownership or late changes. Treat a theme as a hypothesis, not a verdict. Ask what evidence supports it and what evidence might complicate it.

Make meaning together

  1. 1
    Choose a cluster

    Select a group of related observations that matters to the team.

  2. 2
    Ask what connects them

    Describe the shared condition or process without naming a person as the cause.

  3. 3
    Explore effects

    Ask what the pattern changed for the work, customers, or team.

  4. 4
    Check the interpretation

    Invite another explanation and note what is still uncertain.

Sort it

Sort observations by the kind of condition they describe.

  1. A task waited because its next owner was unclear
  2. A review happened after work had moved on
  3. The decision criteria were not visible
  4. Two teams used different versions of the plan

05 / Practice1:20–1:45

Choose a small experiment

Turn one insight into an action the team can test and review.

25 min1 stepActivity: 25 min
5.1

Define an owned next step

Try it · 25 min

Choose an action that is specific, feasible, and easy to revisit.

  • Write an action with an owner and a review point

A useful action changes something the team can actually try. Prefer one small experiment over a broad promise such as “communicate better.” Decide how you will notice whether the change helped, and when you will review it.

Design the experiment

  1. 1
    Select one pattern

    Choose a theme that matters and is within the team's influence.

  2. 2
    Write a specific change

    State what the team will do differently and in which situation.

  3. 3
    Name an owner

    Choose one person to coordinate the action, not to carry all the work alone.

  4. 4
    Set a signal and review point

    Describe what evidence would suggest improvement and when the team will check.

WriteOur experiment, owner, signal of progress, and review point:

ExperimentOwnerProgress signalReview point

Checklist

Before committing

06 / Debrief1:45–2:00

Close and carry learning forward

Review the commitments and end with a clear sense of what happens next.

15 min1 step
6.1

Confirm and close

Reflect · 15 min

Make the record usable and invite a final reflection.

  • Confirm how actions will be tracked

Close the session

  1. 1
    Read back actions

    Confirm each action, owner, progress signal, and review point.

  2. 2
    Choose a record keeper

    Agree where the notes will live and who will share them with the team.

  3. 3
    Invite a final reflection

    Ask each person what they want to carry forward or what remains unsaid.

  4. 4
    Thank the group

    Recognize specific contributions, including careful listening and constructive disagreement.

Saved in this browser only. Nothing is sent anywhere.

End / Your notesEverything you wrote, in one place

  1. 1.1 Settle in and choose a focus

    Work or period under review, and what we hope to learn:

  2. 2.1 Agree how to work together

    Our agreements and what we may share beyond this session:

  3. 3.1 Build a shared picture

    What helped the work? What made it harder?

  4. 4.1 Explore themes without jumping to blame

    Pattern we notice, examples that support it, and questions still open:

  5. 5.1 Define an owned next step

    Our experiment, owner, signal of progress, and review point:

  6. 6.1 Confirm and close

    What is one thing you want the team to remember or do after this retrospective?

  7. 6.1 Confirm and close

    Where the actions will be recorded and when the team will revisit them:

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