Playbook

Turn Retrospective into Improvement

Move from team feeling to prioritized learning points, experiments, and verifiable change.

Outcome

A focused improvement initiative with owner, hypothesis, and review date.

At the end you have

Retro BoardEmotion ClustersAction IdeasPDCA Plan

Decision point

You can decide which improvement experiment the team tests next.

Next step

Run the experiment in daily work, review impact, and adjust working agreements as needed.

Ideal for

Scrum and Kanban teams
Teams after releases or difficult phases
continuous improvement

Not good for

Performance reviews of individuals
acute conflict moderation without safety

Preparation

What should be clear before you start

Roles

Team
Facilitator or scrum master
Stakeholders for systemic blockers if needed

Inputs

events from last iteration
team mood and observations
open improvement or conflict topics

Setup

Set a safe discussion frame
Clarify the purpose of the retrospective
Reserve time for concrete actions

Flow

Method path

0 methods

Completion criteria

At least one concrete improvement experiment is decided.
Owner and review date are set.
Team can name expected effect.
Unresolved topics are transparently parked.

Templates

Artifacts for this playbook

Artifacts stay collapsed until you actually need them.

ChecklistShow template

Working Agreements Checklist

Checklist for concrete, testable team working agreements.

- [ ] Agreement is phrased in an observable way
- [ ] Applies to everyone on the team
- [ ] Contains no pure statements of intent
- [ ] Conflict case is described
- [ ] Review date is set
- [ ] Owner for maintenance is named