WRAP retrospective: Wishes, Risks, Appreciations, Puzzles

What do we wish for, what could go wrong, who deserves thanks, and what don't we understand yet? WRAP checks morale and scans for risks in the same hour.

Wishes

If a genie helped us—what would be true next sprint?

Risks

Known threats or “gotchas” on the horizon

Appreciations

Shout-outs and wins—who/what deserves thanks?

Puzzles

Head-scratchers and open questions we should explore

Use this template — it's free

What a WRAP retrospective is

WRAP stands for Wishes, Risks, Appreciations, Puzzles. Two columns look ahead: what the team would like to be true next sprint, and the threats it can already see coming. One looks back at people: who and what deserves thanks. And one collects what nobody can explain yet. The team writes cards in all four, reads the appreciations aloud, and spends the discussion on the wishes, risks and puzzles that got the most votes.

Where WRAP is stronger than a classic retro:

• It gives uncertainty a home. Most formats ask for opinions: what was good, what was bad, what to change. The Puzzles column asks for questions. "Why do sign-ups drop every Monday?" or "Who decides whether we still support the old Android version?" are neither complaints nor ideas, so they rarely come up anywhere else, and they often point straight at the next problem.
• Risks get named before they hurt. A retro that only looks back finds issues after they have cost you. The Risks column asks what is coming while there is still time to steer around it.
• Thanks are part of the agenda. Appreciation is a full column, not a "kudos" minute squeezed in at the end if there is time left. Teams under pressure need it most and skip it first.
• Wishes show what people care about. "If a genie helped us, what would be true next sprint?" is a planning question in disguise. The answers are often surprisingly modest and specific, and therefore reachable.

When to use it, and when not to

WRAP works well when the team needs both encouragement and foresight:

• before a big milestone — a launch, a migration, a demo for an important customer — when risks are on everyone's mind;
• after a period of change: new people, a new manager, a new product area. The puzzles show where knowledge is missing;
• when morale is low but you cannot afford a session that is only about feelings;
• when retros have turned into problem lists and nobody says thank you anymore;
• every month or so on a long project, as a regular risk check.

Pick something else when:

• You need one concrete fix. WRAP spreads attention across four very different questions. If the team has a clear problem to solve, the KPT retrospective gets to an experiment faster.
• The team is just forming. At a kick-off there is not much to appreciate yet. Hopes & Fears covers the wishes and risks in a two-column session that suits a first meeting.
• The goal itself is unclear. Wishes and risks are hard to judge without a shared destination. The Sailboat starts from the island — the goal — and works back from there.

The four columns

In ProstoRetro the board opens with Wishes, Risks, Appreciations and Puzzles. Below is what belongs in each, and the tests that keep cards from landing in the wrong place.

Wishes: what would be true next sprint

The column asks: if a genie helped us, what would be true next sprint? Ask for a state of things, not a task. "Write more tests" is a task; "we deploy on a Friday and nobody worries" is a wish. Keep the horizon to the next sprint or two, so wishes stay within reach and can turn into a first step.

• Every pull request gets its first review within four hours
• Design and engineering agree on scope before the sprint starts
• We hear about outages from monitoring, not from customers
• The two new developers ship something end to end by the end of the month

Risks: what could go wrong

Known threats and "gotchas" on the horizon. The test: you can phrase it as "if X happens, then Y", and it has not happened yet. Something that is already hurting is a problem, not a risk — it belongs in the discussion, but the action it needs is different.

• The certificate for the mobile login expires in three weeks, and the last renewal failed
• The search migration has no rollback plan
• Only one person can approve database changes, and she is away for most of December
• Nobody has tested the partner API's rate limits at launch traffic

Appreciations: who and what deserves thanks

Shout-outs and wins. The test: a specific person or thing, and the reason. "Thanks, everyone" does not count; "thanks to Leo for staying on the call until the customer could log in again" does. Appreciations can go to things too: a tool, a decision, another team.

• Ana, for rewriting the flaky checkout tests: CI has been green all week
• Support, for tagging every bug report with the app version
• Whoever argued to cut bulk editing from the release — it kept the launch on schedule
• Kenji's setup guide: the new hire had a working laptop by lunch

Puzzles: what we don't understand yet

Head-scratchers and open questions worth exploring. The test against a risk: you cannot yet say whether it is good or bad, or what you would do about it, because you are missing information. A puzzle is written as a question, and its action is usually "who finds out, and by when?"

• Why did page load time double after a release that changed nothing in the frontend?
• Who owns the notification service now that the platform team has split?
• Do customers still use the old dashboard, or is it only us?
• What does "done" mean for the accessibility work?

Use this template — it's free

A 60-minute WRAP agenda

For a team of five to nine people. With a bigger group, give the discussion ten more minutes.

1. Warm-up, 5 minutes. Start with a question that has nothing to do with work; choose one from our icebreaker questions, or let the board open with a built-in icebreaker round that picks the question and who answers.
2. Silent writing, 10 minutes. Everyone fills all four columns. Nobody sees other people's cards until the writing ends, so one person's alarming risk does not set off a chain of similar ones.
3. Appreciations and grouping, 10 minutes. When the cards are revealed, start by reading the appreciations. Then group the wishes, risks and puzzles; the app's AI can propose a first grouping to start from.
4. Voting, 5 minutes. Votes go to the wishes, risks and puzzles the team most wants to talk about. Voting is anonymous, so a risk raised by a junior person gets the same chance as one raised by the lead.
5. Discussion, 20 minutes. Three or four topics, each with its own question. For a wish: "what is the smallest step toward it?" For a risk: "how likely, how bad, and what is the early warning sign?" For a puzzle: "what would we need to know, and who can find out?"
6. Action items, 7 minutes. Each top risk gets an owner who watches it and a mitigation or plan B. Each puzzle gets someone who comes back with an answer. Each wish gets a first step. Give every action a due date.
7. Close, 3 minutes. Go over the owners and dates once more, and ask everyone what they will remember from the session.

If you set the meeting length when creating the board, ProstoRetro divides the hour between phases and topics and keeps the timers running, so a long debate about one risk does not crowd out the puzzles.

Remote facilitation tips

• Sign the thanks, hide the worries. Each person can decide per card whether it is anonymous; cards are anonymous by default. People often want their name on an appreciation and not on a risk that questions a manager's plan.
• Make appreciations visible. Cards can carry images and GIFs, which makes the thanks column the liveliest part of a remote board, and people actually read it.
• Size risks with a quick poll. Before discussing a big risk, run an anonymous single-choice poll: "How likely is it that the migration slips past launch?" A wide spread of answers is itself worth discussing.
• Read the mood before the risks. Open with the anonymous pulse survey. Its results are revealed when the discussion starts; a low score is a cue to give the wishes more time and not spend the whole hour on what could go wrong.
• Treat puzzles as real work. Turn each top puzzle into an action item for someone to investigate. Owners are reminded by email, and the open item reappears when the next retro begins, so questions do not stay open forever.

Variations

Pre-launch WRAP

In the week or two before a release, spend most of the discussion on risks and puzzles. For each top risk, agree on the signal that would tell you it is happening and who is watching for it. Keep the appreciations — a team heading into a launch needs them more than usual.

End-of-project WRAP

When a project wraps up, turn the forward-looking columns toward the next one: wishes for how the next project should run, risks the team expects to carry over, puzzles still unanswered. Appreciations close the chapter properly. For a deeper look at lessons and the decisions ahead, the FLAP retrospective is built for that moment.

WRAP with Next steps

If your discussions keep ending without clear actions, add a fifth column, Next steps, and fill it during the discussion. In ProstoRetro this is a custom template: up to five columns, each with your own name, description and color.

Common mistakes

• Fantasy wishes. "Rewrite everything from scratch" will not happen next sprint. Keep wishes to something the team could make true in a few weeks.
• Risks without owners. A risk everyone agrees on and nobody watches is just a prediction. Every top risk needs a name next to it.
• Skipping puzzles. They do not produce obvious tasks, so they get left for last and run out of time. Give at least one puzzle a slot in every session.
• Generic thanks. "Great job, team" is kind and forgettable. Ask for the person, the act and why it mattered.
• Mixing risks and problems. A problem needs fixing now; a risk needs watching and a plan B. Treat them the same and the risks never get attention until they turn into problems.

FAQ

What does WRAP stand for in a retrospective?

Wishes, Risks, Appreciations, Puzzles: what the team would like to be true, the threats on the horizon, who and what deserves thanks, and the open questions worth exploring.

What is the difference between a risk and a puzzle?

A risk is a threat you can describe — "if this happens, that breaks". A puzzle is something you do not understand well enough to call good or bad. Risks get a mitigation; puzzles get someone who finds out.

How is WRAP different from Hopes & Fears?

Hopes & Fears covers only the forward-looking half: what people hope for and what worries them. WRAP adds appreciations and puzzles, which makes it better for a team that already has a shared history.

How long does a WRAP retrospective take?

About an hour for five to nine people, following the agenda above. A 40-minute version works if you limit the discussion to one risk, one wish and one puzzle.

Can I run a WRAP retrospective online for free?

Yes. ProstoRetro includes the WRAP template at no cost, and anonymous cards make it easier to raise a risk nobody wants to sign. To learn the app, read how to run a great retro, or pick another format from the retrospective templates.