Highlights & Wins

What were our proudest moments this year?

We shipped our biggest product release ever and the launch went smoothly.
Our team grew from 5 to 12 people and onboarding went really well.
We hit our annual revenue target two months early.
Lessons Learned

What did we learn that we'll carry forward?

Investing in documentation early saves us pain later.
Smaller, more frequent releases reduce risk dramatically.
We need to set realistic deadlines and protect focus time.
Goals for Next Year

What do we want to achieve in the year ahead?

Improve our deployment frequency to weekly releases.
Build a stronger culture of feedback and recognition.
Invest in upskilling the team in new technologies.

What is the Year in Review Retrospective?

Wrapping up a year is the perfect moment to pause, celebrate wins, and learn from the bumps along the way. The Year in Review Retrospective gives your team a structured space to look back across the last twelve months, recognise the milestones that mattered, and surface the lessons that will shape a stronger year ahead. Unlike a fast-paced sprint retrospective, this format zooms out to the big picture so everyone can appreciate just how far they've come. Running a Year in Review in TeamRetro is simple and inclusive. Each participant reflects on highlights, challenges, lessons learned, and ambitions for the coming year, then the team groups, votes on, and discusses the themes that resonate most. This annual retrospective encourages honest dialogue, builds shared memory, and turns reflection into momentum. It's a great way to close out a year on a high note while setting clear intentions for what comes next. Whether you're a product team, leadership group, or community gathering, the Year in Review helps celebrate achievements, acknowledge growth, and align on priorities. By the end of the session your team will have a meaningful record of the year, a renewed sense of connection, and a list of action items to carry into the months ahead.

Year in Review retrospective format

Highlights & Wins

What were our proudest moments this year?

This topic invites the team to celebrate the achievements, milestones, and standout moments of the year. Encourage everyone to think broadly across projects, relationships, and personal growth. Start by reminding the team that no win is too small to mention, and use this as a chance to build positive energy before tackling the harder reflections.

Lessons Learned

What did we learn that we'll carry forward?

This topic helps the team distil insights and knowledge gained over the year. Encourage participants to think about both successes and failures and what they taught the group. Look for patterns and recurring themes that could inform how the team works going forward.

Goals for Next Year

What do we want to achieve in the year ahead?

Wrap up the retrospective by looking forward and setting ambitions for the coming year. Encourage the team to be specific and to connect goals back to the lessons learned. This is a great moment to turn reflection into concrete action items and shared commitments.

When to use this retrospective

  • At the close of a calendar or fiscal year to reflect on the past twelve months and set direction for the next.
  • When a team has completed a major program or initiative and wants to capture the bigger-picture learnings.
  • To re-energise and reconnect a team after a long, demanding period of work.
  • When onboarding new leadership who want to understand the team's recent history and trajectory.
  • For communities or organisations wanting to celebrate collective achievements and align on shared goals.

Suggested icebreaker questions

  • If you could sum up your year in a single emoji, which one would it be and why?
  • What's one song that would be on the soundtrack of your past year?

Ideas and tips for your retrospective meeting

  • Send a prompt ahead of time so participants can reflect on the whole year before the session — memories from January can be easy to forget.
  • Keep the celebration of wins front and centre; starting on a positive note sets the tone for honest conversation about challenges.
  • Timebox each topic so you don't spend the whole session reminiscing and run out of time for forward-looking goals.
  • Encourage equal participation by giving everyone quiet time to add ideas privately before grouping and discussing.
  • Turn 'Goals for Next Year' into clear, owned action items so the reflection translates into real momentum.
  • Capture a summary or export the board so the team has a lasting record of the year to revisit later.

Frequently asked questions

When should we run a Year in Review Retrospective?
It works best near the end of a calendar or fiscal year, or after completing a major program. The goal is to step back from day-to-day delivery and reflect on the bigger picture before planning the year ahead.
How long does a Year in Review Retrospective take?
Because it covers a full year of reflection, allow 60 to 90 minutes. Larger teams or those with lots to celebrate may benefit from a slightly longer session with breaks.
How is it different from a sprint retrospective?
A sprint retrospective focuses on a short, recent cycle of work, while a Year in Review zooms out to the entire year. It emphasises celebrating milestones, capturing high-level lessons, and setting annual goals rather than tweaking near-term process.
Who should take part in a Year in Review Retrospective?
Anyone who contributed to the year's work — including team members, leaders, and sometimes cross-functional partners. Broad participation creates a richer, shared picture of what the year was really like.
How do we keep the conversation balanced between celebrating and improving?
Use the structured topics to give equal time to highlights, challenges, lessons, and future goals. Timeboxing each area ensures you celebrate wins without dwelling, and leaves room to turn reflection into action.

New to retrospectives? Read our guide on how to run a retrospective →