End of Year Retrospective

Look back on your team's year and plan the next one

Try this retrospective live

Highlights and achievements

What were the team's most significant accomplishments this year?

We launched a new product feature that was well-received by customers.
Our team successfully transitioned to a new project management tool, improving our workflow.
We exceeded our sales targets for the year, thanks to our collaborative efforts.
Challenges and obstacles

What were the most significant challenges or setbacks the team faced?

We experienced delays in our project timeline due to resource constraints.
Adapting to new processes and tools was initially challenging for some team members.
Communication breakdowns led to misunderstandings and rework in certain areas.
Lessons learned

What lessons did the team learn from the challenges it faced?

We learned the value of clear and frequent communication, especially during times of change.
We miss deadlines when we skip resource planning and risk checks.
Continuous learning and upskilling are essential to stay ahead of industry trends.
Areas for improvement

What aspects of our work or processes could be improved in the coming year?

Simplifying our project management process to cut duplicate work and bottlenecks.
Improving cross-functional collaboration and knowledge sharing across teams.
Investing in professional development opportunities for team members.

What is the End of Year retrospective?

An end of year retrospective is a chance for your team to look back on the past 12 months together. You celebrate what went well, dig into the setbacks and work out what to change before next year's planning starts. The template has four topics: highlights and achievements, challenges and obstacles, lessons learned, and areas for improvement. Working through them in that order moves the conversation from the year's wins to what you'll do differently, and the lessons column keeps setbacks from turning into a blame session. A year is long enough that people remember it differently. Reflecting as a group gives everyone the same picture of what happened, and that shared picture is a better starting point for next year's goals than any one person's memory.

End of year retrospective format

Highlights and achievements

What were the team's most significant accomplishments this year?

Encourage participants to share specific examples of successful projects, milestones, or initiatives. Celebrate both team and individual achievements.

Challenges and obstacles

What were the most significant challenges or setbacks the team faced?

Encourage open and honest discussion about the difficulties encountered. Avoid blame or criticism, and focus on understanding the root causes.

Lessons learned

What lessons did the team learn from the challenges it faced?

Make the point that setbacks are worth learning from, and talk about how to use those lessons to improve. Encourage participants to share how they've grown personally.

Areas for improvement

What aspects of our work or processes could be improved in the coming year?

Encourage participants to name specific areas where the team could work better or more efficiently. Focus on improvements that are actionable and realistic.

When to use this retrospective

  • At the end of a calendar or fiscal year, to review the past 12 months.
  • During annual planning or goal-setting, so next year's plan builds on this year's lessons.
  • After finishing a major project or initiative, to capture lessons learned.
  • When new team members join, to give them context on the year that's just happened.
  • Whenever you want to step back from sprint-level detail and look at the bigger picture.

Suggested icebreaker questions

  • What was the most memorable moment or highlight of the past year for you?
  • If you could describe the past year in three words, what would they be?

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

Ideas and tips for your retrospective meeting

  • Set a no-blame tone at the start so people can be honest about the hard parts of the year.
  • Bring a timeline of the year's big moments to jog people's memories.
  • Ask someone to take notes on decisions and action items.
  • Celebrate the wins, and treat failures as lessons to learn from.
  • If discussion drifts toward who caused a problem, bring it back to what the team can change.
  • Turn each area for improvement into a plan with an owner, and check on it in your first retrospective of the new year.

Frequently asked questions

When should we run an end of year retrospective?
Run it in the last few weeks of the year or at your first team meeting in January, while the past 12 months are still fresh.
Who should take part in an end of year retrospective?
The whole team. Everyone remembers a different part of the year, so more voices give you a more accurate list of what to improve.
How is an end of year retrospective different from a sprint retrospective?
It looks back over the whole year instead of one sprint. The discussion stays at a higher level: big wins, recurring problems and lessons that should shape next year's goals.
How long does an end of year retrospective take?
Plan for 60–90 minutes. A year is a lot to cover, so ask people to jot down their highlights beforehand if you want more time for discussion.
What questions should you ask in an end of year retrospective?
This template asks four: what were the team's biggest accomplishments, what challenges did you face, what did you learn from them, and what could you improve next year?

Related templates

New Year Kickoff Retrospective

Close out last year and set this year's team goals.

Project Kickoff Planning

Agree on goals, risks and milestones before work starts.

Project Post Mortem Template

Review any project or incident, capture lessons learned

Fiscal Year-End Review

Review the year's numbers and plan the next one

Ready to run this retrospective?Try this retrospective live