Another debrief. Another page of notes. Make this one change something.
Thirty minutes after a sprint, a launch or a bad week. Everyone reflects privately first, then the team chooses one to three improvements and names who owns each and when you’ll check it stuck.
14-day trial, no card. Runs in your browser.
30 minutes with the team
- Before
- 10 min, everyone
- After
- 15 min, each owner
The problem
The team is honest about what went wrong. Someone writes it up. Then the next piece of work starts and the notes go in a folder with the last three sets. The same frustrations come back a month later, slightly worse.
This session keeps the honesty and adds the part that’s usually missing: a small number of specific changes, each with a name and a date against it.
What you leave with
One to three improvements, each with an owner, a next action, and a review date.
The thirty minutes
- 10 minutes
Before the session, everyone
Write down one thing to keep, one frustration and one thing to try. Private notes stay private unless you choose to share them.
- 5 minutes
Step 1
Share themes, not blame. Agree which observations are facts, which are opinions, and what still needs checking. Keep it about the work and the system, not a person.
- 10 minutes
Step 2
Group what people noticed into keep, change and try. Write possible improvements in plain words. Stop when the themes are clear enough to choose from.
- 8 minutes
Step 3
Place the possible improvements by how much they’d help and how hard they’d be. Pick one to three. Park the rest, visibly.
- 7 minutes
Step 4
For each one chosen: the next action, who owns it, how you’ll know it worked, and the date you’ll review it.
- 15 minutes
After the session, each owner
On the review date, bring what happened. Keep the change, adjust it, or stop it, and say why.
A worked example
- The work
- A six-week build for a client. Delivered on time, but the last ten days were late nights and the client asked for changes on the final day.
- What people wrote privately
- Keep: the daily ten-minute check-in. Frustration: the client only saw the work at the end. Try: show it earlier.
- The themes
- Three of five people wrote some version of “the client saw it too late”. Nobody blamed anyone. One fact was checked: the client had asked for a mid-point look in week two and been told “not yet”.
- The improvements chosen
- Two. Demo to the client on day 8 of every sprint, not at the end. Write the “definition of done” with the client in week one. A third idea, a new ticketing tool, was parked.
- Owners and dates, written in the session
- Ana owns the day-8 demo; next action is to book the slot today; review at the end of the next sprint. Sam owns the shared definition of done; review at the same time.
- Review, one sprint later
- Keep both. The client asked for two changes on day 8 instead of twelve on day 42. No late nights.
Thirty minutes is deliberate. A debrief that runs long turns into a complaint session. The timings are tight so the energy goes into choosing and owning a change, not relitigating the work.
What it doesn't do
It doesn’t score the team, rate individuals or produce a report for anyone outside the room. Private reflections stay private. It produces a short list of changes the team has chosen, with names and dates.
14-day trial, no card. One person pays; the team joins free.
Running a full project retrospective? The longer version is in the catalogue for consultants.