Superpowers

What strengths and wins powered the team forward?

Our pair programming sessions helped us ship the new feature faster than expected.
The team's communication during the incident was super clear and calm.
We caught most bugs early thanks to our solid automated test coverage.
Kryptonite

What weakened the team or slowed us down?

Unclear requirements meant we reworked the same feature twice.
Too many meetings left little time for deep focused work.
Our flaky CI pipeline kept failing and slowed every deploy.
Source of Power

What energizes and motivates the team to keep going?

Seeing real users benefit from what we built keeps me motivated.
Celebrating small wins as a team gives me a boost.
Having autonomy over how I solve problems energizes me.
Call to Action

What heroic steps will we take next?

Let's introduce a definition of ready to avoid unclear requirements.
We'll assign a clear owner to the CI pipeline reliability work.
Block two no-meeting focus afternoons each week.

What is the Man of Steel Retrospective?

The Man of Steel Retrospective uses Superman's story as a frame for your team's review. Superman draws his strength from the sun and is weakened by kryptonite, and the board borrows both ideas: what makes your team strong, what drains it and what keeps it going. The board has four columns. Superpowers is for the strengths, wins and habits that helped the team succeed. Kryptonite names the weaknesses and blockers that slowed you down, kept to processes and situations, not people. Source of Power asks what motivates the team, from seeing users benefit to having a say in how you work. Call to Action turns the discussion into two or three concrete steps for the next sprint. Source of Power is the column that sets this format apart from a standard retro. It gives the team time to talk about motivation and energy, which rarely gets airtime. Use it after a big release, during a long project, or whenever your usual retros have started to feel flat.

Man of Steel retrospective format

Superpowers

What strengths and wins powered the team forward?

Superpowers are the strengths, achievements and habits that helped the team succeed. Ask about both individual and team wins, and what made people feel unstoppable. Push for specifics so the team can repeat them on purpose.

Kryptonite

What weakened the team or slowed us down?

Kryptonite covers the weaknesses, blockers and recurring obstacles that drained the team. Keep the focus on processes and situations, not people, so the discussion stays honest. These items often become the starting point for your actions.

Source of Power

What energizes and motivates the team to keep going?

Superman recharges from the sun, and this column asks what recharges your team. Ask about the people, practices or moments that gave people energy. Knowing these helps the team protect what keeps morale up.

Call to Action

What heroic steps will we take next?

The Call to Action turns reflection into commitment. Help the team define concrete improvements for the next iteration, each with an owner and a date. Keep it to a few high-impact actions so the team can follow through and check progress next time.

When to use this retrospective

  • When standard retrospectives feel stale and your team needs a themed format to get people talking again.
  • After a major release or milestone, to celebrate the wins and be open about what held the team back.
  • With newer or distributed teams, where a playful metaphor makes it easier to share honestly.
  • When you want to check in on motivation as well as delivery, using the Source of Power column.

Suggested icebreaker questions

  • If you could have one superpower at work, what would it be and why?
  • What's your personal kryptonite, the one thing that instantly derails your productivity?

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

Ideas and tips for your retrospective meeting

  • Introduce the superhero theme at the start so everyone understands the metaphor before adding ideas.
  • Keep Kryptonite focused on processes and situations, not individuals, so people feel safe.
  • Timebox each column to keep the energy up and stop the session dragging.
  • Use anonymous input if the team is new or sensitive topics may come up.
  • Limit Call to Action to two or three items so the team can deliver them before the next retro.
  • Start by reviewing the previous Call to Action items to keep the team accountable and show progress.

Frequently asked questions

How long does a Man of Steel Retrospective take?
A typical session takes 45 to 60 minutes for a team of five to eight. Adjust the time per column to your team size and how much discussion each one generates.
When should I use this retrospective format?
Use it when you want more energy in your retros: after a big release, during a long project, or when your usual format feels repetitive.
How is it different from a standard Start, Stop, Continue retrospective?
Start, Stop, Continue sorts ideas by what to change. The Man of Steel Retrospective sorts them into strengths, blockers, sources of motivation and next steps, so it adds a conversation about what keeps the team going.
Do participants need to know the Superman story to take part?
No. Each column has a plain meaning (strengths, blockers, motivation and next steps), so anyone can contribute without knowing the story.
Can I run this retrospective with a remote or distributed team?
Yes. In TeamRetro everyone can add ideas, group them, vote and discuss, either live or asynchronously, so it works for remote and hybrid teams.
Ready to run this retrospective?Try this retrospective live