Shout Out Spectacle

Thank your teammates by name for what they did.

Try this retrospective live

Individual Shout Outs

Who deserves a public thank you this time?

Huge thanks to Priya for jumping in over the weekend to unblock the release. You saved us.
Shout out to Marcus for patiently mentoring the new devs without ever making them feel dumb.
Massive appreciation for the design team who turned around those mockups in record time.
Team Wins

What did we achieve together worth celebrating?

We shipped the new onboarding flow ahead of schedule. Proud of this one.
Our bug backlog is the smallest it's been all quarter.
We pulled off a flawless demo for the leadership team.
Lessons in Generosity

Where did support, sharing, or kindness make a difference?

Pairing on the tricky migration taught me more than reading docs ever could.
Someone always picks up the unglamorous tasks, so let's keep noticing that.
Sharing knowledge in the team channel saved everyone hours of digging.
Future celebrations

What should we commit to and celebrate next?

Let's commit to recognizing each other more consistently, not just at retros.
Next milestone: fully automate our deployment pipeline.
I'd love for us to onboard the new hires smoothly and celebrate their first PRs.

What is the Shout Out Spectacle?

Recognition tends to get lost in the rush of day-to-day delivery. The Shout Out Spectacle sets aside a whole retrospective for it, so your team can thank the people and moments that made a difference, including the work that usually goes unnoticed. The board has four areas. Individual Shout Outs comes first: who deserves a public thank you, and for what? Team Wins moves to what you achieved together. Lessons in Generosity looks at how people helped each other and what made that help work, so you can do more of it. Future celebrations closes the session with goals the team would be glad to celebrate next time. Naming the exact behavior behind a thank you shows everyone what good work looks like. Use it at the end of a sprint or project, after a hard stretch, or with a remote or hybrid team where contributions are easy to miss. Run it alongside your problem-solving retros, not in place of them.

Shout Out Spectacle retrospective format

Individual Shout Outs

Who deserves a public thank you this time?

This is the heart of the Shout Out Spectacle. Ask everyone to name a specific person and the specific thing they appreciated, since concrete examples land better than vague praise. Make sure quieter team members and behind-the-scenes contributors get recognized, not only the obvious heroes.

Team Wins

What did we achieve together worth celebrating?

Move from individuals to what the team achieved together. Capture the big milestones and the small everyday wins, since both keep momentum and morale up.

Lessons in Generosity

Where did support, sharing, or kindness make a difference?

This area is for the moments when people helped one another. Ask what the help was and what made it work. If the team can name what made the support effective, it can repeat it on purpose.

Future celebrations

What should we commit to and celebrate next?

Ask the team for goals or commitments it would be glad to celebrate at the next session. Keep them realistic and shared, and assign owners in TeamRetro so they turn into action.

When to use this retrospective

  • At the end of a sprint or project, when you want to finish on a high.
  • When team morale needs a lift or recognition has been thin in recent weeks.
  • For distributed or hybrid teams, where contributions are easy to miss.
  • After a challenging period, to thank the people whose effort and support got the team through.
  • On a regular cadence, so appreciation becomes a habit and not a one-off.

Suggested icebreaker questions

  • If you could give yourself a fun award for this sprint, what would it be called?
  • Who is someone outside this team who deserves a shout out, and why?

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

Ideas and tips for your retrospective meeting

  • Ask for specifics. Naming the exact action behind a shout out means more than generic praise.
  • Check that recognition is spread fairly, and prompt the group to thank quieter or behind-the-scenes contributors.
  • Read shout outs aloud and let people add reactions or votes to the standout moments.
  • Keep it from becoming a popularity contest by focusing on behaviors and their effect, not personalities.
  • Timebox each section so the celebration stays lively and doesn't drift into a general catch-up.
  • Close by turning the goodwill into commitments with clear owners.

Frequently asked questions

What is a Shout Out Spectacle retrospective?
It's a recognition-focused retrospective in which your team thanks individual contributors, celebrates shared wins and looks at how people helped each other. It ends with goals the team wants to celebrate next time.
How long does a Shout Out Spectacle take?
Most sessions run 30 to 45 minutes for a team of five to eight. Allow extra time for a larger group or if you want to read every shout out aloud.
When should I use this format instead of a standard retrospective?
Use it when morale needs a lift, after a tough stretch, or to close out a project on a high note. Keep running your problem-solving retros as well, since this one focuses on appreciation.
How is it different from a Kudos or appreciation retrospective?
It adds structure to a kudos session. Instead of a single round of thanks, the team moves from individual shout outs to team wins, lessons in generosity and goals for next time.
Can remote and hybrid teams run a Shout Out Spectacle?
Yes. In TeamRetro everyone can add and vote on recognition live or asynchronously, so distributed and behind-the-scenes contributors are as visible as everyone else.

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