Dream Within a Dream Retrospective (Inception Edition)

Move from surface events to the tensions underneath.

Try this retrospective live

Level 1: Reality

What did you notice on the surface this sprint?

We shipped the new onboarding flow on time, which felt great.
Our daily standups were running a bit long this sprint.
Two team members were out sick for several days.
Level 2: The Dream

What recurring patterns or habits are shaping our work?

We keep underestimating how long testing actually takes.
Code reviews tend to pile up toward the end of the sprint.
We're great at starting tasks but slower to finish them.
Level 3: The Subconscious

What hidden tensions or unspoken truths are below the surface?

I feel like we avoid talking about technical debt because it's overwhelming.
There's an unspoken pressure to always say yes to new requests.
Sometimes I'm not sure my work is having real impact.
The Kick (Back to Reality)

What actions will bring us back, stronger than before?

Let's add a dedicated time block for code reviews each day.
We'll start documenting key processes so knowledge is shared.
Let's timebox standups to 15 minutes from now on.

What is the Dream Within a Dream Retrospective?

The Dream Within a Dream Retrospective takes its idea from Christopher Nolan's film Inception, where the characters go down through dreams nested inside other dreams. Your team does the same with the last sprint, starting with what anyone could see and going down a layer at a time toward what people usually leave unsaid. There are three levels and a way back out. Level 1: Reality covers the visible facts and events. Level 2: The Dream looks for patterns and habits that repeat sprint after sprint. Level 3: The Subconscious is for hidden tensions and unspoken truths. The Kick (Back to Reality) turns what came up into a few actions, the way the kick in the film wakes the dreamers. The layers give the conversation a natural order: quick facts first, harder topics once people have warmed up. Use it when your usual format has gone stale or you suspect the real issues aren't being said out loud, and keep the action list short.

Dream Within a Dream (Inception Edition) retrospective format

Level 1: Reality

What did you notice on the surface this sprint?

This is the waking layer, where facts and events are easy to see. Ask people to share what happened without analyzing it yet. Keep the round quick and factual so you have time for the deeper levels.

Level 2: The Dream

What recurring patterns or habits are shaping our work?

One layer down, look past single events to the patterns that keep showing up. Ask what feels familiar from previous sprints. This separates one-off blips from habits worth addressing. Give people a minute of quiet thinking before they share.

Level 3: The Subconscious

What hidden tensions or unspoken truths are below the surface?

This is the deepest layer, where unspoken feelings and tensions sit. Remind the team there are no wrong answers and ask for the frustrations, worries or hopes that don't usually get said. Model openness yourself and listen without judging.

The Kick (Back to Reality)

What actions will bring us back, stronger than before?

In the film, the kick is what wakes the dreamers. Here it's where insights from the deeper layers become a few clear actions, each with an owner. Two or three commitments the team will keep are worth more than a long wish list.

When to use this retrospective

  • When your team has retrospective fatigue and needs a different format to get people talking.
  • When you want to get beneath surface-level observations to root causes and unspoken tensions.
  • When people seem to be holding back, and a gradual move from easy topics to hard ones would help them speak up.
  • When you want a themed session that still ends with concrete actions.

Suggested icebreaker questions

  • If you could design your own dream world, what's the first thing you'd add to it?
  • What's a recurring dream you've had, and what do you think it was trying to tell you?

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 with a quick reference to Inception so people understand the layers before they start.
  • Don't rush the deeper layers. Give people quiet thinking time before they share at Level 3.
  • Watch for one or two voices dominating, and invite quieter members in directly.
  • Keep Level 1 short so you have time and energy for the levels below it.
  • Limit The Kick to two or three actions so the commitments are realistic and owned.
  • Tell the team that Level 3 is a judgment-free zone before you open it.

Frequently asked questions

How long does the Dream Within a Dream retrospective take?
Most teams finish in 45 to 60 minutes. Level 3 usually needs the most time, so leave room for honest discussion there.
When should I use the Inception Edition retrospective?
Use it when your team needs a break from standard formats or wants to get beneath surface observations to root causes and unspoken tensions.
How is this different from a standard 'What went well' retrospective?
A What Went Well retrospective collects observations at one level. This format moves through three, from visible facts to patterns to hidden tensions, before The Kick turns them into actions.
Do participants need to have watched Inception?
No. The film gives the layers a memorable name, but the structure makes sense whether or not people have seen it.
How many people can take part?
It works best with a small team where people can hear each other at Level 3. For larger groups, group responses within each layer to keep the discussion focused.
Why go down to the deeper layers?
Level 3 is where people raise tensions and hopes that rarely come up in everyday work, like pressure to say yes to every request. Those are often the causes behind the patterns at Level 2.

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