Retrospective

Review the work, find the root causes, extract the learning.

Teams work through a series of tailored retrospective questions to review their work from multiple angles, digging into root causes and extracting the key learnings.

Type
Exercise
Time
30 minutes
Group size
4-12 people
Best as
Team review
In depth

A little more detail.

Successful projects are almost always those where everyone had a shared understanding of priorities and good systems for getting work done together. Less successful ones invariably lack both. Participants work through tailored retrospective questions covering what was expected versus what happened, what contributed to success, what could have derailed things, and how the team worked together under pressure. The aim is to surface root causes and real learnings, steering clear of blame or replaying frustrations. Moments of high performance and collaboration are highlighted too: what was done and, equally, how it was achieved. The retrospective becomes a springboard for improvement, with clear themes and actions to guide what comes next.
Outcomes

What you'll leave with.

Teams gain a clear picture of what happened and why, with concrete learnings and actions to carry forward.

BRIEF Facilitation notes

How to run it.

Agree the period you are looking back on with the team leader in advance, then work the group through four questions to understand what happened, why, and what to carry forward. Push past surface answers to the dynamics beneath the outcomes.

one
30 minutes

Brief the group at the start: we are looking at this period, and the aim is to understand what happened, why, and what we can take forward. Then work through four questions in sequence, giving people time to write individually before discussing as a group.

What went well? Capture real successes: outcomes achieved, moments of strong collaboration, decisions that held up. Push for specifics, since 'the way we managed handovers between the two teams during the final week' is more useful than 'the launch.' What was difficult? Name the challenges, blockers, and moments of friction, framed as what we would want to avoid repeating. What impact did we make, and what changed as a result of this team's work? And what have we learned, drawing on the first three: given what went well and what was difficult, what do we now know that we did not before, about our work, our team, or how we operate together?

Then identify two or three clear themes and name them explicitly. The retrospective is most valuable when it surfaces the dynamics beneath the outcomes, so push past surface answers with questions like 'what made that difficult?' and 'how were we operating as a team at the time?' The goal is root causes and real learnings.

When to use it

Use Retrospective when a team wants to review a project or period and pull real learning from it. Structured questions look at what happened and why, digging past surface accounts to root causes and leaving the team with clear themes and actions.

Use it when

  • A team wants to review a project or period and extract learning.
  • You want to get past surface accounts to root causes.
  • The team needs clear themes and actions to carry forward.

Not the right tool when

  • There is no completed work or period to look back on.
  • The group will use it to assign blame instead of learning.
Used in

Workshops that feature this tool.

Use it with your team

This tool works best in a well-facilitated room.

Using this tool with a skilled facilitator means that discussions are focused, time is used efficiently, and the group moves toward consensus, making the session productive and impactful.