Rocket Ship Retrospective: Launch Your Team to New Heights
January 22, 2025
RetroFlow Team
The RetroFlow team builds free retrospective tools and writes practical guides for agile teams. We have helped thousands of teams run better retros.
The Rocket Ship retrospective uses the exciting metaphor of space exploration to help teams visualize their journey toward ambitious goals. By representing propelling forces as rocket fuel and obstacles as gravity or asteroids, this format creates an engaging and memorable retrospective that resonates with teams working on innovative or ambitious projects.
If your team is working on something that feels like a moonshot or you want an energizing visual format, the Rocket Ship retrospective delivers both engagement and actionable insights.
What Is the Rocket Ship Retrospective?
The Rocket Ship retrospective uses space travel as a metaphor for your team’s project journey:
| Element | Metaphor | What It Represents |
|---|---|---|
| Stars/Moon ⭐🌙 | Destination | Our goal or mission |
| Rocket Fuel 🔥 | Propulsion | What’s pushing us forward |
| Gravity ⬇️ | Pull back to Earth | What’s holding us back |
| Asteroids ☄️ | Space hazards | Risks and obstacles ahead |
| Mission Control 📡 | Ground support | External support and stakeholders |
| Crew 👩🚀 | Astronauts | Team dynamics and collaboration |
The visual nature of this format makes abstract concepts tangible and creates excitement around your team’s mission.
Why the Rocket Ship Format Works
Aspirational Metaphor
Space exploration naturally evokes:
- Ambition — Reaching for the stars
- Innovation — Doing what hasn’t been done
- Teamwork — No solo missions to space
- Precision — Every detail matters
Comprehensive Coverage
The Rocket Ship format covers:
- Goals (stars/moon)
- Enablers (fuel)
- Blockers (gravity)
- Risks (asteroids)
- Support systems (mission control)
High Engagement
The space metaphor:
- Feels exciting and aspirational
- Appeals to teams working on innovative projects
- Creates memorable retrospectives
- Works especially well for tech teams
The Rocket Ship Elements Explained
Stars/Moon ⭐🌙 — Our Destination
The stars or moon represent your team’s ultimate goal—the mission you’re working toward.
What belongs here:
- Sprint or project goals
- Product vision
- Key milestones
- Definition of success
- Long-term objectives
Examples:
- “Moon: Launch beta to 1,000 users”
- “Stars: Achieve product-market fit”
- “Destination: Zero downtime deployment”
- “Mission: Complete platform migration”
- “Target: Series A funding readiness”
Prompts:
- What’s our mission this sprint?
- Where are we trying to land?
- What does mission success look like?
Rocket Fuel 🔥 — What’s Propelling Us
The rocket fuel represents everything giving your team thrust and momentum.
What belongs here:
- Effective processes and practices
- Helpful tools and technologies
- Team skills and motivation
- Supportive leadership
- Recent wins building momentum
Examples:
- “High-octane fuel: New CI/CD pipeline shipping faster”
- “Booster: Product owner’s crystal-clear priorities”
- “Fuel: Team’s enthusiasm for the project”
- “Propulsion: Excellent pair programming sessions”
- “Thrust: Automated testing catching bugs early”
Prompts:
- What’s giving us momentum?
- What’s propelling us toward our goal?
- What would slow us down if we lost it?
Gravity ⬇️ — What’s Pulling Us Back
The gravity represents the forces trying to pull your team back to Earth—obstacles and drag slowing your ascent.
What belongs here:
- Current blockers
- Technical debt
- Process inefficiencies
- Resource constraints
- Legacy systems
Examples:
- “Heavy gravity: Technical debt in payment module”
- “Drag: Waiting for external approvals”
- “Pull: Too many meetings fragmenting focus”
- “Weight: Unclear requirements slowing development”
- “Gravity well: Legacy system integration”
Prompts:
- What’s pulling us back toward Earth?
- What’s creating drag on our mission?
- What weight can we jettison?
Asteroids ☄️ — Risks Ahead
The asteroids represent future dangers—hazards in your flight path that could damage the mission.
What belongs here:
- Known risks not yet addressed
- Technical risks
- Team risks (burnout, turnover)
- External dependencies
- Timeline or scope risks
Examples:
- “Asteroid field: Scalability concerns as users grow”
- “Incoming rock: Key team member might leave”
- “Hazard: Security audit in two sprints”
- “Debris: Vendor contract expiring”
- “Space junk: Accumulating technical debt”
Prompts:
- What could damage our mission if we don’t address it?
- What hazards are in our flight path?
- What keeps mission control worried?
Mission Control 📡 — External Support
The mission control represents the support systems and stakeholders helping guide your mission.
What belongs here:
- Leadership support
- Stakeholder relationships
- External resources
- Cross-team dependencies
- Organizational backing
Examples:
- “Strong signal: Executive sponsorship”
- “Communication link: Good relationship with design team”
- “Support: IT team’s quick response times”
- “Ground crew: Helpful documentation”
Crew 👩🚀 — Team Dynamics
The crew focuses on how the team is working together on this mission.
What belongs here:
- Team collaboration
- Communication quality
- Skill coverage
- Team morale
- Knowledge sharing
Examples:
- “United crew: Great collaboration across time zones”
- “Skilled astronauts: Strong technical expertise”
- “Crew bonding: Team building activities working”
When to Use the Rocket Ship Retrospective
| Situation | Why Rocket Ship Works |
|---|---|
| Innovative projects | Space metaphor matches ambitious work |
| Tech-focused teams | Resonates with engineers and developers |
| Moonshot initiatives | Language matches the scale |
| Teams needing energy | Exciting metaphor re-engages teams |
| Product launches | ”Launch” language fits naturally |
| Startups | Captures the startup journey feeling |
When to Choose Other Formats
- Very short retros (< 30 min): Use Start Stop Continue
- Emotional focus: Use Mad Sad Glad
- Nature-loving teams: Use Sailboat or Mountain Climber
- First retrospective ever: Start with simpler format
How to Run a Rocket Ship Retrospective
Before the Meeting
Preparation:
- Schedule 45-60 minutes
- Prepare visual board with rocket, stars, asteroids
- Draw or use a digital template
- Define the “mission” (current goal)
- Review previous retrospective action items
Step-by-Step Facilitation
Step 1: Set the Stage (5 minutes)
Introduce the metaphor:
“Today we’re doing a Rocket Ship retrospective. Imagine our team is on a mission to reach the stars.
We’ll explore:
- Stars/Moon — Our mission destination
- Rocket Fuel — What’s propelling us forward
- Gravity — What’s pulling us back
- Asteroids — Risks in our flight path
Let’s map our mission!”
Establish the destination first: “Our target this sprint is [goal]. Is the whole crew aligned on our destination?”
Step 2: Silent Brainstorming (10 minutes)
Have team members add items to each area:
- Use sticky notes (physical or digital)
- One idea per note
- Place in appropriate zone on the visual
Facilitator tip: Walk through each element: “Add your fuel items… now gravity… now asteroids…”
💡 RetroFlow makes visual retrospectives easy—free, no signup required.
Step 3: Share and Discuss (20 minutes)
Go through each area systematically:
Recommended order:
- Stars/Moon — Confirm the mission
- Fuel — Start with what’s working
- Gravity — Address current drag
- Asteroids — Discuss future risks
For each item:
- Author explains briefly
- Group discussion on impact
- Note connections between elements
Discussion prompts:
- “Is this high-octane fuel or just fumes?”
- “Can we escape this gravity or do we need more thrust?”
- “How close is this asteroid? When might we hit it?”
Step 4: Prioritize (5 minutes)
Use dot voting to identify:
- Most critical gravity to overcome
- Most dangerous asteroids to avoid
- Essential fuel to maintain
Step 5: Create Action Items (10 minutes)
Convert priorities into actions:
| Element | Item | Action |
|---|---|---|
| Gravity | Slow code reviews | Implement review rotation, 24hr SLA |
| Asteroid | Key person risk | Cross-training sessions this sprint |
| Fuel | Great standups | Document format for other teams |
Framework for actions:
- Gravity: How do we reduce the pull?
- Asteroids: How do we navigate around them?
- Fuel: How do we maintain or increase thrust?
Step 6: Close (5 minutes)
- Summarize action items
- Celebrate mission progress
- Optional: “Are we on course for landing?”
Rocket Ship Retrospective Template
⭐ ⭐ ⭐
⭐ ⭐
🌙 MISSION TARGET
⭐
☄️
☄️ ASTEROID
ASTEROID |
\ /
\ 🚀 /
\ /\ /
\ / \ /
/ \ /
/ 🔥 \
/ FUEL \
/__________\
|
|
⬇️ GRAVITY
(What's pulling us back)
|
____________________
🌍 EARTH
(Where we started)
Digital Template Layout
For digital tools, create zones:
┌──────────────────────────────────────────────────────────────────────┐
│ ROCKET SHIP RETROSPECTIVE │
├────────────────┬────────────────┬────────────────┬──────────────────┤
│ 🔥 FUEL │ ⬇️ GRAVITY │ ☄️ ASTEROIDS │ 📡 MISSION │
│ │ │ │ CONTROL │
│ What's │ What's │ Risks in │ │
│ propelling │ pulling us │ our path │ External │
│ us forward │ back │ │ support │
│ │ │ │ │
│ │ │ │ │
└────────────────┴────────────────┴────────────────┴──────────────────┘
⭐ MISSION: [Your Goal Here]
Sample Items for Each Element
Mission (Stars/Moon) Examples
- Launch product to first 100 customers
- Complete infrastructure migration
- Achieve 99.9% uptime
- Ship mobile app v2.0
- Reach profitability milestone
Fuel Examples
- Automated deployment pipeline
- Strong team collaboration
- Clear product roadmap
- Executive support for project
- New monitoring tools
Gravity Examples
- Technical debt slowing features
- Manual QA process
- Waiting for external team
- Unclear priorities
- Meeting overload
Asteroid Examples
- Key team member considering leaving
- Scalability concerns
- Security vulnerabilities to address
- Competitor launching similar product
- Upcoming compliance deadline
For discussion prompts that pair well with this format, see our retrospective questions guide.
Tips for Facilitating Rocket Ship
Make It Visual
- Draw the rocket — Even simple drawings help
- Show trajectory — Arrow from Earth to stars
- Use colors — Orange for fuel, red for asteroids
- Add countdown — “T-minus X sprints to launch”
Extend the Metaphor
During discussion, use space language:
- “That’s a lot of drag—do we need more thrust?”
- “Can we plot a course around this asteroid?”
- “What would give us more fuel for the journey?”
- “Is mission control aware of this risk?”
Connect to Mission Progress
Help team see actual progress:
- “Last sprint we were in orbit, now we’re approaching the moon”
- “We’ve navigated past three major asteroids this quarter”
- “Our fuel efficiency has improved significantly”
For Remote Teams
- Use digital whiteboard (Miro, Mural, Figma)
- Pre-build the space visual template
- Enable simultaneous editing
- Add rocket animation or progress indicator
Variations on Rocket Ship
Simple Three-Column
For shorter retrospectives:
- Fuel — What’s propelling us
- Gravity — What’s holding us back
- Mission — Where we’re headed
Extended Space Mission
Add more elements for longer projects:
- Launch pad — Where we started
- Orbit — Stable achievements
- Black holes — Things to avoid at all costs
- Space station — Milestones along the way
- Supplies — Resources we need
Multi-Mission Program
For programs with multiple goals:
- Near orbit — Sprint goal
- Moon — Quarter goal
- Mars — Year goal
Common Mistakes to Avoid
Mistake 1: Vague Mission
Problem: “Our mission is to be awesome” Fix: Make missions specific: “Launch payment feature by sprint end”
Mistake 2: All Gravity, No Fuel
Problem: Session becomes complaint fest Fix: Start with fuel to establish positive energy
Mistake 3: Ignoring Asteroids
Problem: Only focusing on current issues Fix: Explicitly ask about future risks in the flight path
Mistake 4: Not Tracking Trajectory
Problem: Every retro feels like you’re still on the launch pad Fix: Note progress since last retrospective
Related Visual Formats
If your team enjoys the Rocket Ship metaphor, try:
- Sailboat Retrospective — Wind, anchors, and rocks
- Hot Air Balloon Retrospective — Hot air vs. sandbags
- Mountain Climber Retrospective — Summit, gear, obstacles
- Speed Car Retrospective — Engine, brakes, bridge
For non-visual formats:
- Start Stop Continue — Simple columns
- 4Ls Retrospective — Liked, Learned, Lacked, Longed For
See all options in our sprint retrospective formats guide.
Get Started
Run a Rocket Ship retrospective for free with RetroFlow — no signup, no limits, ready in 30 seconds.
Summary
The Rocket Ship retrospective uses an exciting space metaphor:
- Stars/Moon ⭐🌙 — Our mission destination
- Fuel 🔥 — What’s propelling us forward
- Gravity ⬇️ — What’s pulling us back
- Asteroids ☄️ — Risks in our flight path
It’s ideal for ambitious projects, tech teams, and anyone who needs an energizing retrospective format. Run it in 45-60 minutes with focus on maintaining fuel, overcoming gravity, and navigating around asteroids.
Related Articles
- Sprint Retrospective Formats Guide - 30+ formats
- Sailboat Retrospective - Similar visual format
- Mountain Climber Retrospective - Achievement-focused format
- How to Facilitate a Retrospective - Facilitation tips