EdAuthor activity template

Team retrospective that turns observations into action

A retrospective creates a structured pause to examine how work happened, not only what was delivered. Individual input broadens the evidence, thematic discussion builds shared understanding and prioritisation keeps the close focused.

Leave with a decision, not just a wall of comments.

A small team is reviewing its last project cycle. They collect observations, look for shared themes and choose one improvement to test next.

Illustration of a project team holding a retrospective around a meeting table with edauthor improvement priorities displayed on a large screen.

  1. Hear the experience

    Give everyone a way to contribute before the discussion starts. Keep observations about the work specific and useful.

    edauthor room screen: What helped us do good work, and what got in the way?

    Early feedback helped; unclear handovers and late changes made the work harder.

  2. Look for the connection

    Ask the team to name the themes they hear. Read the shared picture as a prompt for conversation, not a verdict.

    edauthor room screen: Which themes should we explore together?

    Clarity, feedback and handovers connect several different observations.

  3. Pick the next experiment

    Choose a small improvement, agree an owner and decide when to review it. The ranking helps focus the conversation.

    edauthor room screen: Which one change would improve our next cycle most?

    A clearer handover checklist leads this example. The team can now agree who will try it and when to revisit it.

Actual edauthor screens with demonstration responses. Scene artwork is illustrative.

Purpose and outcome

Gather more than the loudest views and agree a small number of useful improvements.

Prepare before the session

Set up the activity around one clear purpose and decide how the responses will shape what happens next.

  • Define the period, project or event being reviewed
  • Set expectations for constructive and non-blaming contributions
  • Decide who will own and revisit the agreed actions

Run the activity

Guide participants through a visible sequence with enough time to think, contribute and learn from the emerging results.

  • Collect observations
  • Find the themes
  • Explore causes
  • Prioritise
  • Agree action

Frequently asked questions

What is the purpose of a retrospective?

A retrospective helps a group learn from how it worked and agree improvements for the next period or project.

How many actions should a retrospective produce?

One or two well-owned actions are often more useful than a long list that the team cannot realistically complete.

Create a free EdAuthor account