Personal Growth Retrospective

Set personal goals and get your team's help reaching them.

Try this retrospective live

Improve

What actions can you personally take to improve the next sprint?

I will block out focused development time each morning to improve my coding skills
I want to speak up more in planning meetings to share my ideas
I'll practice active listening by taking notes during team discussions
Support

How can the team help you going forward and why is that important?

I'd appreciate more code reviews to help improve my technical skills
Having a mentor would really help me grow in my role faster
I need more context on business decisions to make better technical choices
Grateful

What are you grateful for at work?

I'm thankful for Sarah's patience in explaining complex concepts to me
The flexible work hours have helped me maintain a better work-life balance
I appreciate how the team supported me during my recent family emergency

What is the Personal Growth Retrospective?

The Personal Growth retrospective turns the usual retro around. Instead of asking how the team's process went, it asks each person what they want to get better at, and what the team can do to help. The board has three columns. Improve is for actions you'll take yourself before the next sprint, like asking for feedback after each presentation. Support is where you ask the team for something specific, such as more code reviews or a chance to shadow a client meeting, and say why it matters. Grateful closes the session with thanks for the people and conditions that helped you this period. Because people say their goals out loud and the team hears exactly what help is wanted, support stops being a vague offer and becomes something someone can act on. It works well before performance reviews, after a big milestone, or any time the team wants to know each other better. Start by sharing a growth area of your own; it makes it easier for others to do the same.

Personal Growth Retrospective Format

Improve

What actions can you personally take to improve the next sprint?

This column is about what each person will do themselves. Ask for specific improvements people can make on their own before the next sprint, not changes they're waiting on from others. A SMART goal helps where it fits, but a clear single action is enough.

Support

How can the team help you going forward and why is that important?

Here people ask the team for help. Encourage specific requests, like a code review on every pull request or a chance to shadow a client call, and ask each person to say why it matters to them and to the team. Note who offers to help so the request doesn't get lost.

Grateful

What are you grateful for at work?

Close on gratitude. Ask people to name what they're thankful for and why it mattered, whether that's a colleague's patience, a stretch project or flexible hours. Specific thanks tells people which of their habits to keep.

When to use this retrospective

  • When people on the team want clearer direction on their professional development
  • Before performance reviews, to help each person set goals they've already talked through
  • When the team wants to get better at supporting each other
  • After a major project milestone, to reflect on what each person learned

Suggested icebreaker questions

  • What's one skill you learned as a child that still helps you today?
  • If you could instantly master any professional skill, what would it be and why?

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

Ideas and tips for your retrospective meeting

  • Go first and share one of your own growth areas; it makes it easier for others to be candid
  • Ask for specific commitments. "Get better at presenting" is a wish; "ask for feedback after every demo" is an action
  • Keep the focus on what each person can do, not on blaming others or circumstances
  • Follow up on support requests in the next team meeting or in one-on-ones
  • Run it every quarter so people can see how far they've come
  • Let people keep sensitive development topics private, and follow up one-on-one instead

Frequently asked questions

What is a personal growth retrospective?
It's a retrospective about individual development. Each person adds what they'll improve themselves, the support they'd like from the team and what they're grateful for, so the team leaves knowing how to help each other.
How do you run a personal growth retrospective?
Give everyone a few minutes to add notes privately in the Improve, Support and Grateful columns. Then go around the team so each person shares their goal and support request, and agree who will help with what.
When should you run a personal growth retrospective?
Use it when people want direction on their development, ahead of performance reviews, or after a major milestone. It also helps when the team wants to strengthen how it supports each other.
How often should a team run it?
Every quarter works for most teams. That leaves enough time for people to make progress on their goals before the next session.
What if people don't want to share personal goals with the whole team?
Let them keep sensitive items private and follow up in a one-on-one. The Grateful column is a low-risk way in for anyone who isn't ready to talk about their own development.

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