Meeting types · Retrospective

Retrospective minutes, without the note-taker.

Retros fail not because teams lack insight but because the insight is never written down as something a specific person will do.

Try your first meeting free30 minutes free · No credit card · Works on your phone
In the room: The delivery team, a facilitator or scrum master, and sometimes a product owner. Managers attending changes what people say, which is worth deciding deliberately.Improvements agreed, each with a named owner and a sprint to land inThe specific incidents that prompted each oneWhat went well and is worth protecting, not just what went badly

The recurring failure of retrospectives is not that people won't speak up. It is that a team spends an hour diagnosing a real problem, agrees something should change, writes 'improve communication' on a sticky note, and repeats the whole exercise next sprint. The discussion is genuinely good; the output is unfalsifiable. Nobody can say at the next retro whether communication improved, which is precisely why the same sticky note reappears.

Facilitation is part of why. Whoever is running the retro is managing the room, watching who has not spoken and keeping a difficult conversation productive. They cannot simultaneously be the person capturing the moment where a vague complaint turned into a specific, actionable change — which usually happens once, briefly, forty minutes in. Whoever holds the pen also quietly decides what gets recorded as the team's view.

Recording the session lets the facilitator facilitate. GetNotes transcribes it with speaker labels and extracts action items with owners, so what leaves the room is a short list of committed changes attached to names rather than a photograph of a whiteboard nobody opens again. The only real test of a retro is whether anything is different three weeks later, and that turns almost entirely on whether a name got attached to a change.

A word of caution particular to retros: they only work if people can be blunt. A record that circulates beyond the team turns a retro into a performance. Agree up front who sees the notes — most teams keep the transcript within the team and share only the agreed actions — and honour it. Psychological safety is worth more than a complete archive.

Where it earns its keep

The same problem, fourth sprint running

Deployment pain comes up again. Everyone nods, everyone agrees it is bad, nothing changes because nobody ever owned it. A written record across four retros makes the pattern undeniable and forces the escalation that should have happened in sprint one.

The facilitator who wanted to contribute

The scrum master has the sharpest observation about how the estimate went wrong, but they are running the board and watching the clock. Not having to also be the scribe frees them to be a participant for the ten minutes it matters.

A tense retro after a bad release

A failed release makes for a charged room. The record needs to hold the systemic causes and the fixes agreed, without becoming a document of who said what about whom that someone quotes back later.

How GetNotes works

  1. Record or upload. Hit record on your phone or laptop in the room — or drop in an audio file you already have. No bot joins anything.
  2. It writes it down. Every word transcribed, every speaker labelled, in 90+ languages including ones that switch mid-sentence.
  3. Share the minutes.Summary, decisions, and action items with owners — ready before everyone's back at their desk.

Questions, answered

Won't recording a retro stop people being honest?

It can, and that risk deserves a straight answer rather than reassurance. Ask the team, agree that the transcript stays within the team and that only the agreed actions get shared wider, and let anyone ask for the recording to be paused. GetNotes stores recordings privately to your account by default, and deleting a meeting removes the audio and transcript permanently.

Does GetNotes pull out retro action items automatically?

Yes. GetNotes extracts action items with owners and deadlines from the conversation, which for a retro means the improvements the team actually committed to, attached to the person who volunteered. That is precisely the material that dissolves when a retro's only artefact is a wall of sticky notes photographed on the way out.

How do I keep the notes focused on actions rather than blame?

Mostly through how you run the retro — GetNotes writes up what the room produced, so a blameful hour produces a blameful record. What it does help with is separating the agreed improvements into a clear action list, so the shareable output is the set of changes rather than the transcript of how the team got there.

Can I compare this retro with the last one?

Each meeting is stored with its own transcript and minutes, so opening the previous retro's action items before this one starts is a two-minute habit worth building. Reviewing which of last sprint's commitments actually landed is the single change that most reliably stops retros becoming theatre.

Other meeting types

Daily standupOne-on-oneWorkshopLanguages26 pagesProfessions16 pages

Your next meeting can write its own minutes.

Record it, and see. Your first meeting is free — thirty minutes, any language, no credit card.

Try your first meeting free