Most year-end retrospectives are either skipped or forgotten by January. Here's a three-phase approach that makes them worth doing.
Why Year-End Retrospectives Matter
December is a natural inflection point. Projects wrap up, goals are reviewed, and teams reflect on what the year actually looked like versus what they planned. A well-run retrospective captures that energy and turns it into better plans for the year ahead.
A poorly run one wastes an afternoon and leaves people feeling like nothing will change.
The Three-Phase Approach
Phase 1: The Past — What happened?
Start by building a shared timeline of the year. Ask team members to contribute significant events — launches, setbacks, team changes, moments of pride, moments of frustration. Use a physical or virtual whiteboard.
Once the timeline is visible, ask: "What would we have done differently?" This is not about blame — it's about identifying patterns that the team has the power to change.
Phase 2: The Present — What do we appreciate?
This is the most underrated part of any retrospective. Go around the team and ask each person to offer one specific word of appreciation to a colleague. Not generic praise — something observed, something that made a difference.
"I appreciated how you stepped in when the deployment went wrong at 11pm." "I appreciated that you always made time to explain things, even when you were under pressure."
This exercise takes ten minutes and changes the room. Teams often discover things about each other they assumed were invisible.
Phase 3: The Future — What do we wish for?
Ask everyone to create a wishlist: what would they like to be different next year? Keep it broad — personal development, team processes, tooling, culture.
The key discipline here: not every wish will come true, and that's fine. Acknowledge it explicitly. The value is in surfacing what people care about, not in promising everything.
From the wishlists, identify the top three things the team collectively wants to prioritise. These become your commitments for Q1.
Making It Stick
The retrospective is only as good as what happens next. Before you close:
- Assign an owner to each Q1 commitment
- Set a date to review progress (ideally mid-January)
- Share a summary with the whole team within 48 hours
Teams that do this consistently find that their year-end retrospectives become something people look forward to — not another box to tick before the holiday break.