- 🎁 Unwrapping Round
- 🙏 Wishes
- ⚠️ Risks
- 💛 Appreciations
- 🧩 Puzzles
WRAP Retrospective
WRAP is a four-column retrospective format built around four questions that rarely all get asked in the same session: what do we wish were different, what risks should we be watching, who deserves genuine recognition, and what are we still confused about?
Most retrospective formats ask teams to analyse the past or commit to the future. WRAP does both, but with a softer touch. Wishes sidesteps blame by framing improvement as aspiration rather than complaint. Puzzles acknowledges that not everything needs an answer today — some things just need to be named. Risks keeps the forward-looking planning that often gets swallowed by discussion about what already went wrong. Appreciations closes the loop on human recognition, which is easy to skip in formats that are purely process-focused.
The result is a format that creates psychological safety not by accident but by design.
When to choose WRAP
- When the team needs to speak honestly without triggering defensiveness. The Wishes column reframes "we have a problem" into "here's what I'd love to see change" — a subtle linguistic shift that keeps people contributing rather than defending.
- When risks are accumulating quietly. Most teams carry quiet worries between retrospectives. The dedicated Risks column gives those a legitimate home before they become actual incidents.
- When team morale is fragile. The Appreciations column ensures no one leaves the session feeling unrecognised, which matters more than usual after difficult sprints.
- When the team is in an ambiguous phase. New project, post-reorg, unfamiliar tech — these are moments where Puzzles does real work. Naming what nobody understands reduces isolation and often surfaces that the confusion is shared.
- After a sprint with mixed signals. Not quite good, not quite bad — the kind of sprint where the standard "what went well / what didn't" framework produces thin cards. WRAP's four distinct lenses generate richer material when the usual questions feel forced.
Warm up: Unwrapping Round
The format is called WRAP — so open the session by unwrapping it together.
- Start icebreaker music as the team joins. Pick something low-key and neutral — you want people relaxed, not buzzing.
- Switch on Brainstorming mode so responses stay anonymous until revealed.
- Post the prompt in 🎁 Unwrapping Round: "In one sentence or one emoji — what's on your mind as you unwrap this sprint?"
- Use the AI Icebreaker Bot to offer an alternative if the team wants something lighter — for example: "If this sprint were a gift, what was in the box?"
- Reveal together — the facilitator switches off Brainstorming mode. Read each card aloud without analysis. Just let the team see each other's starting points.
The whole thing takes 5 minutes. Leave the Unwrapping Round cards on the board — they're a useful reference if the discussion later drifts far from where people started.
🎁 Unwrapping Round
What's on your mind as you unwrap this sprint?
Your one-card warm-up before the main board opens. Add it during the warm-up above, then leave it there. It's a visible snapshot of team sentiment at the start of the session — useful to glance back at if the retro mood diverges sharply from those opening answers.
🙏 Wishes
What do you wish had gone differently?
Wishes are improvement suggestions rewritten as personal aspirations. "I wish we'd had clearer acceptance criteria at sprint start" carries less blame weight than "acceptance criteria were always unclear" — but it carries the same information. The distinction matters in rooms where directness triggers defensiveness, or where some team members are reluctant to name problems unless they're framed constructively.
Encourage specificity. "I wish the CI pipeline ran in under 10 minutes" is far more actionable than "I wish things were faster." Vague wishes are hard to convert into actions. Specific ones almost convert themselves.
⚠️ Risks
What could derail the next sprint?
Risks is a forward-facing column designed to surface what the team is quietly worried about but hasn't said in any other forum. An upcoming dependency that hasn't been confirmed. A team member going on leave mid-sprint. A product requirement likely to change after development starts. A third-party integration that keeps behaving unpredictably.
The value here isn't analysis — it's naming. Something the whole team can see on the board and talk about is already less dangerous than something everyone knows but no one has said. Every Risk that gets voted to the top should produce at least one action before the session ends: a decision made, an owner assigned, or a conversation scheduled.
💛 Appreciations
Who deserves recognition this sprint?
Appreciations covers people, but also tools, processes, and decisions that made the sprint better. "Appreciated that product kept scope frozen this sprint" is a valid Appreciation. "Huge thanks to Priya for picking up the on-call rotation when I was away" is also valid.
Read all Appreciations aloud at the end of the session. This is not optional — a card that goes unread is a recognition that never landed. Hearing them with the whole team present is the point.
🧩 Puzzles
What are you confused or uncertain about?
Puzzles holds the questions the team doesn't have answers to yet. Why did the deployment fail on Friday but not on Thursday? What's the roadmap decision that keeps getting deferred? What does "done" actually mean for the discovery work next sprint? These aren't failures — they're open loops that deserve space.
Some Puzzles will produce immediate answers in the discussion. Others will become action items: "find out who owns this decision by Wednesday." A few might just sit there, acknowledged and unresolved — which is also fine. The goal is not to solve everything; it's to make sure nothing carries its confusion invisibly into the next sprint.
Facilitating the discussion
After the Unwrapping Round warm-up, a time split that works well for a 60-minute session:
- Wishes — 15 minutes (group by theme; convert the top two into concrete experiments)
- Risks — 20 minutes (highest-impact column; every top-voted Risk should leave with an owner)
- Appreciations — 10 minutes (read aloud, no discussion needed)
- Puzzles — 15 minutes (answer what you can; assign the rest as open questions to resolve before next retro)
Use anonymous voting across Wishes and Risks. The most useful Puzzles are often the ones quieter team members are carrying — anonymity surfaces them reliably.
Variations
WRAP without the warm-up. For time-pressured teams, skip the Unwrapping Round and start directly with the four core columns. A 45-minute WRAP session runs cleanly with a strict timebox.
Async WRAP. Share the board link 24 hours before the sync session. Ask team members to fill in Wishes, Risks, and Puzzles asynchronously. The live session focuses entirely on discussion, voting, and action items — effective for distributed teams across multiple time zones.
WRAP as a mid-sprint check-in. Run just the Risks and Puzzles columns as a 20-minute mid-sprint checkpoint. It doesn't replace the full retrospective but is a lightweight way to name emerging concerns before they fully materialise. Pair it with a Pulse Survey for ongoing visibility between retros.
Related formats
- Wish & Wonder retrospective — The closest relative on the Wishes axis. Wish & Wonder is purely aspirational and non-confrontational; WRAP adds Risks and Puzzles to create a more complete picture of team state.
- Hot Air Balloon retrospective — Shares the forward-looking risk dimension (Storm Clouds). Use Hot Air Balloon when visual metaphor helps the team engage; use WRAP when direct language works better.
- Agile retrospective — The foundational format. WRAP draws on the same instinct to surface what's working, what isn't, and what needs to change — reorganised through four psychologically distinct lenses.
Frequently Asked Questions
What is the WRAP retrospective template?
The WRAP retrospective template is a four-column agile format covering Wishes, Risks, Appreciations, and Puzzles. It gives teams four distinct lenses in a single session: aspirational improvement framing (Wishes), proactive threat identification (Risks), explicit peer recognition (Appreciations), and space for unresolved questions (Puzzles). Unlike formats that focus purely on what happened last sprint, WRAP is designed to surface things teams typically suppress — quiet worries, unspoken confusion, and recognition that never quite gets said. The warm-up column, Unwrapping Round, sets the tone with a low-stakes icebreaker that gets everyone contributing before the main board opens.
When should you use the WRAP retrospective?
Use the WRAP retrospective when your team needs psychological safety baked into the format itself — when direct criticism triggers defensiveness, when risks are accumulating quietly between retros, or when team members deserve recognition that keeps getting skipped. It's particularly effective after uncertain or ambiguous sprints where the standard what-went-well / what-didn't framing produces thin cards. Use it when the team is newly formed, when trust is still developing, or when you sense there are things nobody is saying but everyone is thinking.
How do you run a WRAP retrospective effectively?
To run an effective WRAP retrospective, follow these steps:
- Set the stage — Open with a mood check-in and walk through the four columns: Wishes, Risks, Appreciations, Puzzles
- Warm up — Start icebreaker music and switch on Brainstorming mode. Ask everyone to add one card to 🎁 Unwrapping Round: "In one sentence or emoji — what's on your mind as you unwrap this sprint?"
- Reveal — Read the Unwrapping Round cards aloud together, then move to the main board
- Brainstorm — Give 10 minutes for silent anonymous brainstorming across Wishes, Risks, Appreciations, and Puzzles
- Group and sort — Group and sort similar cards, especially in Wishes and Risks
- Vote — Use anonymous voting to prioritise. Focus discussion time on Risks and Wishes; read all Appreciations aloud at the end without discussion
- Create action items — Assign owners to top Risks and Wishes. Convert unanswered Puzzles into open questions with a deadline to resolve
- Share summary — Export and share the retro summary with the team
How is WRAP different from Wish & Wonder?
WRAP and Wish & Wonder both use aspirational language, but they're built for different purposes. Wish & Wonder is optimistic by design — it reframes everything positively and avoids confrontation. WRAP pairs Wishes with a dedicated Risks column, which introduces forward-facing pragmatism that Wish & Wonder doesn't have. WRAP also separates recognition into its own Appreciations column and adds Puzzles for unresolved questions, making it a more complete picture of team state. Use Wish & Wonder when morale needs lifting and you want a light touch. Use WRAP when you need honest reflection on risks and unknowns alongside the positivity.
What are some alternatives to the WRAP retrospective?
If you're looking for different retrospective formats, consider these alternatives:
- Wish & Wonder retrospective — When you want purely aspirational framing without the explicit Risks and Puzzles structure
- Hot Air Balloon retrospective — When you want a visual metaphor combined with forward risk planning (Storm Clouds) that mirrors WRAP's Risks column
- Agile retrospective — When you want the most universally understood format covering what went well, what didn't, and what needs to change
- Sailboat retrospective — When metaphorical thinking helps the team engage more openly with sensitive topics
Experience a better retro
Create a retro in seconds & see for yourself.