Year in Review Retrospective

Look back on the year, then set next year's goals.

Try this retrospective live

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?

The end of a year is a good time to stop and look at the whole thing, not only the last sprint. The Year in Review Retrospective gives your team a structured way to look back across twelve months, recognize the milestones that mattered and agree on what to carry into next year. The board has three areas. Highlights & Wins is for the proudest moments, from big releases to personal growth. Lessons Learned covers what the year taught the team, including the hard parts and the mistakes. Goals for Next Year turns those lessons into specific ambitions. Everyone adds ideas privately first, then the team groups them, votes and discusses the themes that come up most. It works for product teams, leadership groups and communities alike. Send a prompt a few days before so people can think back to January, and export the board afterward so you have a record of the year to revisit next December.

Year in Review retrospective format

Highlights & Wins

What were our proudest moments this year?

Invite the team to celebrate the year's achievements, milestones and standout moments. Ask people to think across projects, relationships and personal growth, and remind them that no win is too small. Starting here builds goodwill before the harder reflections.

Lessons Learned

What did we learn that we'll carry forward?

Help the team pull out what the year taught it. Ask about successes and failures and what each one showed, then look for patterns that should change how the team works next year.

Goals for Next Year

What do we want to achieve in the year ahead?

Close by looking forward. Ask for specific goals and link each one back to a lesson from the previous area. This is where reflection becomes concrete actions and shared commitments.

When to use this retrospective

  • At the end of a calendar or fiscal year, to look back on the past twelve months and set direction for the next.
  • When the team has finished a major program or initiative and wants to capture the big-picture lessons.
  • To reconnect a team after a long, demanding stretch of work.
  • When new leadership joins and wants to understand the team's recent history.
  • For communities or organizations that want to celebrate what they achieved together and agree 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?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Send a prompt a few days ahead so people can think back over the whole year. Memories from January fade fast.
  • Start with Highlights & Wins; a positive opening makes the honest conversation about lessons easier.
  • Timebox each area so reminiscing doesn't eat the time you need for next year's goals.
  • Give everyone quiet time to add ideas privately before the group discussion, so every voice gets on the board.
  • Turn Goals for Next Year into clear actions with owners, so the plan survives January.
  • Export the board or write a short summary so the team has a record of the year to look back on.

Frequently asked questions

When should we run a Year in Review Retrospective?
Near the end of a calendar or fiscal year, or after finishing a major program. The point is to step back from day-to-day delivery and look at the bigger picture before you plan the year ahead.
How long does a Year in Review Retrospective take?
Allow 60 to 90 minutes, since you're covering a full year. Larger teams, or teams with a lot to celebrate, may want a longer session with a break.
How is it different from a sprint retrospective?
A sprint retrospective looks at a short, recent cycle of work. A Year in Review covers the whole year, so it spends more time on milestones, big lessons and annual goals and less on near-term process tweaks.
Who should take part in a Year in Review Retrospective?
Anyone who contributed to the year's work: team members, leaders and sometimes cross-functional partners. The more people contribute, the more complete the picture of the year.
How do we keep the conversation balanced between celebrating and improving?
Give each of the three areas its own timebox. Highlights & Wins is for celebrating, Lessons Learned is where the hard parts belong, and the timebox keeps enough room for Goals for Next Year.
What questions does a Year in Review retrospective ask?
Three: what were our proudest moments this year, what did we learn that we'll carry forward, and what do we want to achieve in the year ahead?

Related templates

WWE Smackdown Showdown Retrospective

Tag-team your sprint review with a wrestling theme.

Working, Not Working Retrospective

Sort what's working from what isn't, then fix it.

Quarterly Retrospective

Step back from the sprints and review the whole quarter.

Baby Steps Retrospective

Pick one small change your team will actually finish.

Ready to run this retrospective?Try this retrospective live