New Year's Resolutions Retrospective

Look back, let go and set resolutions that stick.

Try this retrospective live

Looking Back

What are we proud of from the past year?

We shipped our biggest product release ever and the whole team rallied behind it.
I'm proud of how we supported each other through a tough Q3.
We finally cleared most of our technical debt backlog.
Leaving Behind

What habits or practices should we stop in the new year?

Too many meetings with no clear agenda or outcome.
Last-minute scope changes that derail our sprint plans.
Letting our documentation fall out of date.
Resolutions

What goals or commitments do we want to make this year?

Protect at least one no-meeting day each week for deep work.
Improve our test coverage to 80% by mid-year.
Run a regular retro every sprint without exception.
Support Needed

What help do we need to make these resolutions stick?

We need leadership to protect our focus time from interruptions.
Let's set up a monthly check-in to review progress on our goals.
A budget for training and conferences would help us grow.

What is the New Year's Resolutions Retrospective?

A new year is a natural point for a team to look back and plan ahead. The New Year's Resolutions Retrospective gives your team a structured way to celebrate last year's wins, name what held you back and agree on the goals and habits you want to carry into the months ahead. It combines a standard retrospective with the clean slate a new year brings. The session runs through four connected conversations: looking back on the year, letting go of habits that no longer help, defining the resolutions you'll commit to and naming the support you'll need to keep them. Leaving Behind matters as much as the resolutions themselves, because dropping an old habit is often what frees up time for a new one. Moving from reflection to commitment gives the team a shared direction and turns vague hopes into a few specific commitments with owners. Run it in early January, at the start of a fiscal year or at any natural milestone. A resolution without support tends to fade by spring, so the last column asks what help the team needs to keep each one.

New Year's Resolutions retrospective format

Looking Back

What are we proud of from the past year?

This column is for celebrating the achievements, milestones and growth from the year that's ending. Invite big wins and small ones, and recognize individual and team contributions. Starting on a positive note gives the team energy for the forward-looking conversations that follow.

Leaving Behind

What habits or practices should we stop in the new year?

Use this column to surface the behaviors, processes or distractions that held the team back. Keep it constructive: this is about deliberately letting go of what no longer helps, not about blame. Focus on patterns instead of individuals so people feel safe to contribute.

Resolutions

What goals or commitments do we want to make this year?

This is the heart of the retrospective: the resolutions the team will commit to. Ask for goals that are specific, measurable and meaningful. Push the team to pick a few resolutions with real impact instead of a long list, so the commitments feel achievable and stay top of mind.

Support Needed

What help do we need to make these resolutions stick?

Resolutions often fail without the right support. Use this column to identify the resources, accountability and changes the team needs to follow through. Record clear actions with owners so each resolution becomes a commitment someone is responsible for.

When to use this retrospective

  • At the start of a new calendar or fiscal year, when people are already reflecting and planning.
  • When you want a year in review and goal setting in a single session.
  • To bring a team back together after a holiday break or a major milestone.
  • When motivation is dipping and the team needs a shared direction again.

Suggested icebreaker questions

  • If you could give the past year a movie title, what would it be?
  • What's one personal habit you're hoping to start in the new year?

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

Ideas and tips for your retrospective meeting

  • Keep resolutions specific and few. Three to five shared goals are far more achievable than a long wish list.
  • Spend real time on the wins before moving to what should change, so the session starts on a positive note.
  • Give each resolution an owner and a check-in schedule so it doesn't fade once the meeting ends.
  • Make it safe to discuss what to leave behind. Talk about patterns and processes, not individuals.
  • Bring the resolutions back in later retros to track progress through the year.
  • Use anonymous brainstorming so quieter team members can add their ideas.

Frequently asked questions

When is the best time to run a New Year's Resolutions Retrospective?
It works best at the start of a calendar or fiscal year, but you can run it at any milestone where the team wants to review the last period and set new goals.
How long does a New Year's Resolutions Retrospective take?
Most teams take 60 to 90 minutes, depending on team size and how much each topic sparks. Allow extra time if you want detailed plans for each resolution.
How is this different from a regular sprint retrospective?
A sprint retrospective looks at the last sprint. This one reviews the whole year and sets goals for the year ahead.
How many resolutions should a team commit to?
Aim for three to five shared resolutions. A few goals the team cares about are more likely to stick than a long list competing for attention.
How do we make sure our resolutions actually happen?
Give each one an owner, agree on how often you'll check in and review the resolutions in later retrospectives.

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