Field guideTeam Retrospective

Facilitator guide

Facilitating a Team Retrospective

A practical guide to helping a team learn from recent work and agree on useful changes

120minutes · 5 sessions

For
Team leads, project facilitators, and colleagues who want to run constructive retrospectives
Length
2 h
Format
Self-paced
Prepared by
Mara Ellison (fictional)

000 / Contents5 sessions

  1. 01Arrive and set the conditionsWarm-up · 1 step0:00–0:10
  2. 02Agree on a useful frameConcept · 1 step0:10–0:25
  3. 03Gather observationsPractice · 1 step0:25–1:00
  4. 04Choose an experimentPractice · 1 step1:00–1:40
  5. 05Close and follow throughDebrief · 1 step1:40–2:00

Before you begin

You will leave with

  • Prepare a retrospective that fits the team’s context and working agreements
  • Guide a balanced discussion of what helped, hindered, and surprised the team
  • Turn observations into specific, owned experiments
  • Close the session with clear follow-up and feedback

01 / Warm-up0:00–0:10

Arrive and set the conditions

Help people settle in, understand the purpose, and agree how to make the conversation useful.

10 min1 stepActivity: 10 min
1.1

Open the retrospective

Try it · 10 min

Create a clear, respectful start and gather a quick sense of how people are arriving.

  • State the purpose and boundaries of the discussion
  • Invite each participant to contribute without pressure

A retrospective is a structured conversation about how work happened, not a performance review. Keep the focus on the team’s process, decisions, and working conditions rather than assigning blame.

Name the period or milestone in scope. Explain what the team can influence and what must be escalated elsewhere.

Start the session

  1. 1
    Welcome the team

    Thank people for making time. State the work period being discussed and the aim: learn and improve how the team works.

  2. 2
    Check the room

    Invite a brief word, phrase, or silent written response about how people are arriving. Allow participants to pass.

  3. 3
    Set expectations

    Explain how notes will be captured, who will see them, and how the team will choose follow-up actions.

02 / Concept0:10–0:25

Agree on a useful frame

Set working agreements and choose a prompt that keeps the discussion grounded in the work.

15 min1 step
2.1

Make the conversation safe and specific

Read · 15 min

Use clear agreements and neutral questions to support honest discussion.

  • Establish practical agreements for respectful participation
  • Use prompts that ask about observable events and effects

Psychological safety means people can raise questions, concerns, and mistakes without expecting humiliation or retaliation. It does not require agreement; it does require respectful attention and a fair chance to contribute.

Ask about events and effects. “The handoff arrived after testing began” is more useful than “That team is careless.” Separate what was observed from what people infer.

Working agreements to adapt

  • Describe events before interpreting motives
  • Make space for different perspectives
  • Share airtime and allow people to pass
  • Treat sensitive details with care
  • Turn criticism toward a change the team can test

03 / Practice0:25–1:00

Gather observations

Collect evidence about what helped, what hindered, and what surprised the team.

35 min1 stepActivity: 35 min
3.1

Map the work experience

Try it · 35 min

Give participants quiet time to contribute before opening a group discussion.

  • Collect observations from across the team
  • Distinguish events from assumptions and interpretations

Start with individual reflection. Quiet writing gives people time to think and reduces the chance that the first speaker sets the whole story. Invite examples from different stages of the work, including handoffs, decisions, tools, and interruptions.

Cluster notes by shared theme without erasing disagreement. Ask what happened, when it happened, and what effect it had. Keep names out of shared notes unless they are needed and appropriate.

Collect and explore observations

  1. 1
    Write privately

    Ask participants to note moments that helped the work, made it harder, or surprised them. Encourage concrete examples.

  2. 2
    Share and cluster

    Invite people to place notes on the board. Group related observations while keeping distinct experiences visible.

  3. 3
    Ask for context

    For each theme, ask what happened and what effect it had on the work. Check whether the group has evidence or is making an assumption.

  4. 4
    Capture open questions

    Record unresolved questions separately. Avoid trying to solve every issue during the observation phase.

WriteRecord a useful observation: what happened, when it happened, and what effect it had.

04 / Practice1:00–1:40

Choose an experiment

Move from recurring themes to a practical change the team can try and review.

40 min1 stepActivity: 40 min
4.1

Design a small, testable change

Try it · 40 min

Select a priority and shape it into a clear experiment with an owner and a review point.

  • Prioritize a theme using impact and team influence
  • Write an experiment that can be observed and reviewed

A useful retrospective action changes something the team can influence. Prefer a small experiment over a broad intention. “Improve communication” is difficult to test; “For the next release, post a handoff summary before testing starts” is observable.

Name who will coordinate the experiment, what signal will show whether it helped, and when the team will review it. An owner coordinates follow-through; the change remains a team responsibility.

Turn a theme into an experiment

  1. 1
    Choose a priority

    Compare themes by their effect on the work and the team’s ability to influence them. Ask who is affected and what evidence supports the choice.

  2. 2
    Describe the change

    Complete this sentence: “During [work or situation], we will [specific action] so that [intended effect].”

  3. 3
    Set a signal and review point

    Choose an observable sign of progress, such as fewer late handoffs or clearer decision records. Agree when to check whether the experiment helped.

  4. 4
    Confirm coordination

    Ask for a volunteer to coordinate the experiment and report back. Keep the action visible in the team’s normal work system.

WriteDraft the team’s experiment and follow-up plan.

Checklist

Before agreeing to an experiment

05 / Debrief1:40–2:00

Close and follow through

Confirm commitments, make room for final reflections, and protect time for follow-up.

20 min1 step
5.1

End with clarity

Reflect · 20 min

Summarize the learning, check how the process felt, and make the next step visible.

  • Confirm the team’s experiment and follow-up plan
  • Gather feedback on the retrospective process

Read back the experiment in plain language. Confirm that the coordinator, progress signal, and review point are understood. Record the agreement where the team already tracks work so it does not disappear after the meeting.

Close by asking what was useful about the conversation and what would make a future retrospective better. Thank people for specific contributions, including raising uncertainty or a difficult issue.

Close the conversation

  1. 1
    Read back the agreement

    Summarize the experiment, coordinator, signal, and review point. Invite corrections before closing.

  2. 2
    Check the experience

    Ask participants what helped them contribute and what could improve the next discussion. Offer a written response option.

  3. 3
    Make follow-up visible

    Add the experiment to the team’s normal work-tracking place and make sure the review point is remembered.

End / Your notesEverything you wrote, in one place

  1. 1.1 Open the retrospective

    What is in scope for this conversation? What is outside the team’s control?

  2. 2.1 Make the conversation safe and specific

    Write the working agreements you want visible during the discussion.

  3. 3.1 Map the work experience

    Record a useful observation: what happened, when it happened, and what effect it had.

  4. 4.1 Design a small, testable change

    Draft the team’s experiment and follow-up plan.

  5. 5.1 End with clarity

    What did the team learn, and what would make the next retrospective more useful?

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