🛸 Among Us: Crew Edition

Suit up, crewmates! Let’s complete tasks, unmask blockers, and eject issues to keep our project spaceship running smoothly. Discuss what’s working well, what’s suss, and how we can boost team trust for a stellar sprint!
45–60 min
4-10 people
Based on: What Went Well, What Went Wrong, What We Want to Improve
🛸 Among Us: Crew Edition

Template Columns

âś… Completed Tasks (No Impostors Detected)

Share the missions and team moments that were completed smoothly, keeping our project ship flying.

Base column: What Went Well
🚨 Sabotages & Sus Issues

Reveal what nearly spaced us—challenges, blockers, or 'impostor' obstacles that hindered our sprint.

Base column: What Went Wrong
🛠️ Emergency Meeting: Fixes & Strategies

Pitch ideas for improvements, new team strategies, or process upgrades to keep impostors at bay.

Base column: What We Want to Improve

About this template

The Among Us: Crew Edition retrospective invites teams to reflect on successes, uncover hidden blockers, and brainstorm improvements in a fun, gamified space theme.

When to use this template

Use this format after sprints when you sense hidden challenges or want to boost team trust and openness. It’s especially effective when a project feels off-track or needs a morale lift.

How to facilitate

1

Set the context by welcoming everyone and explaining the Among Us theme to lighten the mood and encourage open sharing.

2

Invite team members to post highlights under Completed Tasks (No Impostors Detected), celebrating smooth wins and successful teamwork.

3

Move to Sabotages & Sus Issues, encouraging honest sharing of blockers, close calls, and suspicious challenges that may have slowed progress.

4

Transition to Emergency Meeting: Fixes & Strategies. Have the team suggest targeted improvements, process tweaks, or experiments to address the identified issues.

5

Group similar items in each column, discuss root causes, and clarify any 'suss' observations to ensure everyone is on the same page.

6

Prioritize the most impactful strategies or fixes, assign clear next steps, and agree who will champion or monitor each action item.

7

Close the retrospective by acknowledging the contributions, reinforcing team trust, and optionally awarding a fun, virtual crew achievement or badge.

Pro Tips

Use playful language and supportive humor to reduce defensiveness when discussing blockers or mistakes.

If a blocker feels 'suss,' ask follow-up questions to get to the real cause without blame or finger-pointing.

For each improvement idea, clarify who will take ownership to ensure accountability.

Keep the atmosphere light but focused; too much game reference can distract from action planning.

Check in briefly at the start to see how comfortable everyone feels with the gamified format, adjusting as needed.

FAQ

How do I prevent finger-pointing during the 'Sabotages & Sus Issues' discussion?

Frame issues as 'team challenges' rather than individual errors. Focus discussions on what went wrong, not who caused it.

What if some team members aren’t familiar with Among Us?

Give a quick, friendly intro to the game’s theme and remind everyone it serves as a metaphor for collaboration and spotting blockers, not a requirement to play.

How do we keep the retrospective productive despite the playful theme?

Balance fun with focus by clearly transitioning from celebration to problem-solving, and always finish with concrete action items.

Can this format work for non-technical or cross-functional teams?

Absolutely. The themes are broad and can be adapted for any group aiming to uncover hidden issues and build stronger collaboration.

Want a custom template?

Create a retrospective template tailored to your team's needs with our AI-powered generator

Try AI Template Generator

At a glance

  • Duration

    45–60 min

  • Team Size

    4-10 people

  • Columns

    3 columns

  • Base Format

    What Went Well, What Went Wrong, What We Want to Improve

Tags

team building
gamified
trust
reflection
blockers
agile
fun

Ready to get started?

Use this template to run your next retrospective