Sesame Street Shuffle Retrospective

A character-themed retro that makes honest feedback easier.

Try this retrospective live

Sunny Days (What made us happy?)

What brought sunshine and good vibes to our work?

Pairing on the tricky integration task actually turned into a fun afternoon.
We shipped the release a day early and nobody had to work the weekend.
The new onboarding doc got a shout-out from a customer, which felt great.
Grouchy Bins (What frustrated us?)

What felt grumpy, annoying, or got in our way?

The flaky test suite kept failing for reasons unrelated to our changes.
Too many context switches this sprint — I never got into deep focus.
Requirements changed mid-sprint without a clear heads-up.
Curious Questions (What do we want to learn?)

What are we curious about or want to explore further?

I'd love to understand why our build times have crept up lately.
Could we experiment with trunk-based development next sprint?
What would it take to automate the release checklist?
Count On It (What should we commit to?)

What actions can we count on and commit to next?

We'll add a code-review SLA of one business day.
I'll set up an alert so we catch staging outages sooner.
Let's protect two no-meeting focus blocks each week.

What is the Sesame Street Shuffle retrospective?

The Sesame Street Shuffle is a lighthearted retrospective built around the characters of Sesame Street. Many people grew up with them, so the prompts need no explanation, and the playful framing makes it easier to share a frustration you might otherwise keep to yourself. The board has four areas. Sunny Days is for what made the team happy. Grouchy Bins, in the spirit of Oscar the Grouch, is the place to vent about frustrations and blockers. Curious Questions is for the open questions and ideas the team wants to explore, and Count On It, a nod to Count von Count, is where you tally up a few actions to commit to. It suits new or distributed teams still building rapport, teams coming off a tough sprint, and anyone tired of their usual format. In TeamRetro, people add ideas on their own, group and vote on them, and finish with two or three actions that have owners.

Sesame Street Shuffle retrospective format

Sunny Days (What made us happy?)

What brought sunshine and good vibes to our work?

Start on a sunny day. Ask the team for the wins and the moments that made the work enjoyable, including the small ones. Opening with what went well makes the tougher topics easier to raise afterward.

Grouchy Bins (What frustrated us?)

What felt grumpy, annoying, or got in our way?

Take a page from Oscar the Grouch and give people permission to vent about frustrations and blockers. Keep the focus on situations and processes, not individuals, and remind the team that naming a problem is the first step to fixing it.

Curious Questions (What do we want to learn?)

What are we curious about or want to explore further?

This area is for open questions and things the team would like to understand better. Ask 'why?' the way a curious Elmo would, without judgment. The answers often expose a knowledge gap or an idea worth trying.

Count On It (What should we commit to?)

What actions can we count on and commit to next?

Count von Count loves tallying things up, and this final area is where you count your commitments. Help the team agree on a small number of achievable actions, give each an owner and keep the list short so it gets done before the next retro.

When to use this retrospective

  • After an intense sprint, when your team needs a lighter retrospective.
  • With new or distributed teams that are still building trust.
  • When quieter team members need an easier way into the conversation.
  • When your standard retro format feels stale and participation is dropping.

Suggested icebreaker questions

  • Which Sesame Street character best matches your mood this sprint, and why?
  • If your team were a Sesame Street duo, who would you be and who's your partner?

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

Ideas and tips for your retrospective meeting

  • Lean into the theme at the start. It gives people permission to be candid.
  • Timebox each character topic so the fun doesn't crowd out the discussion and the actions.
  • Use anonymous idea entry in TeamRetro for Grouchy Bins so people are honest about their frustrations.
  • Group similar ideas before voting so the discussion stays on the themes that matter most.
  • Limit Count On It to two or three actions with clear owners so they actually get done.
  • Watch who's talking, and invite quieter people in so the loudest characters don't take over.

Frequently asked questions

What is the Sesame Street Shuffle retrospective?
It's a character-themed retrospective based on Sesame Street. Your team shares what made it happy, what frustrated it and what it's curious about, then commits to a few actions.
How long does a Sesame Street Shuffle retrospective take?
Plan for 45 to 60 minutes, depending on team size. Timeboxing each of the four character topics leaves time for the actions at the end.
When should I use this retrospective format?
Use it when your team needs a lift, when a new or distributed team is still building rapport, or when your usual format has started to feel repetitive.
How is it different from a standard Start, Stop, Continue retro?
Both end in actions. Start, Stop, Continue asks directly about behaviors, while the Sesame Street Shuffle adds a space to vent and a space for open questions, which can surface feedback a more formal format misses.
Can I run this retrospective with a remote team?
Yes. In TeamRetro everyone adds ideas, groups them, votes and agrees on actions together, either live or asynchronously.
Does the theme distract from getting real outcomes?
Not if you keep it moving. Count On It closes the session with concrete commitments that each have an owner, so the theme helps people talk without replacing the outcome.

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