A team meeting held at the end of a project, sprint, or incident, where participants reflect on what worked, what didn't, and what to change next time. The classic format is three columns: keep doing, stop doing, start doing — though variants abound (sailboat, 4Ls, mad/sad/glad). Retrospectives only work if participants feel safe being candid, which means the meeting must be structured to surface uncomfortable truths without punishing the messenger. Action items from retrospectives should be specific and few — three concrete commitments are worth more than fifteen vague intentions. AI meeting copilots help retrospectives by capturing the conversation itself (so participants can listen back to themes they noticed in the moment) and by extracting and tracking the resulting commitments through to the next retro.