Air Travel Journey Retrospective

Air Travel Journey retrospective format

Takeoff

What gave us a strong start and momentum?

Takeoff is the start of the flight: the preparation and early wins that got the team off the ground. Ask what set you up well at the start of the project or sprint, from clear goals to good planning, and celebrate whatever built early momentum.

Turbulence

What disruptions or obstacles shook us up?

Turbulence is the bumps, blockers and surprises that disrupted the flight. Keep it blameless and about the problem, not the person. Ask people to be specific, so each item can turn into an improvement later.

Cruising Altitude

What kept things running smoothly along the way?

Cruising altitude is the steady, reliable part of the flight: the practices and habits that kept the team flying smoothly. Ask what worked consistently and what the team wants to protect or repeat. Naming these makes good habits easier to keep.

Landing

How did we finish and what did we deliver?

Landing is about the outcome: how the team reached its destination and how the arrival felt. Ask whether goals were met and what would make the next landing smoother. It's also a natural place to note lessons for the next flight.

When to use this retrospective

• At the end of a sprint or project, to look back on the whole thing from start to finish.
• When you want a metaphor-based alternative to a standard went-well, needs-improvement retro.
• After a bumpy or eventful delivery, to work out what caused the turbulence and how to avoid it next time.
• When you're introducing a team to retrospectives and need a framework that's easy to pick up.
• To celebrate a successful launch while still capturing honest lessons.

Suggested icebreaker questions

• What's the most memorable flight you've ever taken, and why?
• If your last sprint were a flight, would it have been smooth, bumpy, or a white-knuckle ride?

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

Ideas and tips for your retrospective meeting

• Set the scene by asking the team to picture the project as a flight. People find it easier to contribute once they can see the picture.
• Timebox each phase so the conversation moves from takeoff to landing without getting stuck in turbulence.
• Ask for specifics in Turbulence, so each blocker becomes a clear improvement instead of a vague complaint.
• Keep the tone blameless: talk about the journey and the system, not individuals.
• Use grouping and voting in TeamRetro to find the themes that matter most before you agree on actions.
• Capture concrete action items for the next flight so the retro leads to real change.

Frequently asked questions