← Back to blogMeeting Tips

12 Retrospective Ideas, Picked by What's Wrong With Your Retro

November 9 2026 · 6 min read

Quick answer: The best retrospective idea is the one that fixes your retro's specific problem, not the most creative one. If nobody talks, collect answers silently or anonymously before anyone speaks. If the same complaints come back every sprint, review last sprint's action items first. If the team is fine but bored, swap Start/Stop/Continue for Sailboat or the 4Ls for one session.

A retrospective is a short meeting at the end of a sprint or project where the team looks at how it worked, not what it built, and agrees on one or two things to change. Most lists give you 50 formats and no way to choose. This one is sorted by what's going wrong.

Which retrospective format should you use?

| If your retro... | Try | |---|---| | Is quiet, or the same two people talk | Silent writing, anonymous pre-retro question | | Repeats the same complaints every sprint | Action-item review, Five Whys | | Follows a bad sprint or an incident | Timeline | | Works fine but feels stale | Sailboat, 4Ls, Starfish | | Has 12 or more people | 1-2-4-All | | Gets 20 minutes, not 60 | One-word check-in plus one question | | Closes out the year | Year-in-review timeline |

Changing the format every sprint is overrated. A new template doesn't make people more honest. What changes a retro is who speaks first, whether answers have names on them, and whether last sprint's actions happened. Most of the ideas below work on one of those three.

When nobody talks

1. Silent writing first

Everyone writes their points privately for five minutes before anyone speaks. Remote, that's a shared doc where people type at the same time. Then read them out and group them.

The first person to speak sets the frame. Silent writing gives everyone a blank page.

2. Anonymous pre-retro question

Send one specific question the day before: "What actually slowed us down this sprint?" Answers come back with no names. You walk in already knowing the themes.

This is the strongest fix for a quiet retro: nobody goes first, and nobody has to criticize the tech lead's decision in front of the tech lead. Truveal Voice does this part. You write the question and share a link, people answer anonymously without logging in, and the AI clusters the answers into themes. Three rounds are free. We covered how to bring those themes into the session in anonymous sprint retro feedback.

3. Lean Coffee

Everyone suggests topics, the team dot-votes, and you discuss them in order on a timer of five to eight minutes each. Good for teams that talk fine once a topic is on the table but never raise it themselves.

When the same complaints come back every sprint

4. Action-item review

Spend the first ten minutes of the retro on last retro's action items. Did each one happen? If not, why not? Only then move to new points.

This is the most skipped step in retros and the reason "too many meetings" shows up eight sprints in a row. If you do one thing from this list, do this.

5. Five Whys

Take the one recurring complaint and ask "why?" until you hit something the team controls. "Deploys are slow" → why? → "Reviews wait two days" → why? → "Only two people can approve infra changes." That last one is an action item. "Deploys are slow" isn't.

One problem per retro. Five Whys on four problems is an hour of philosophy.

After a rough sprint or an incident

6. Timeline

Draw the sprint as a line from day one to the last day. Everyone adds events (a release, an outage, a scope change, a sick week) and marks how they felt at each point. Then talk through the dips.

A timeline keeps a hard retro about events instead of people. "Wednesday, the scope changed and nobody told QA" is easier to discuss than "you didn't tell QA." Skip themed templates here. After a bad week, a gimmick reads as not taking it seriously.

When the retro works but feels stale

These are the formats most lists lead with. They're fine, but they don't fix a quiet room or a broken follow-up.

7. Sailboat

Draw a boat. Wind pushed the team forward, anchors held it back, rocks are risks ahead, the island is the goal. The rocks are the point: they get people thinking a sprint ahead, which went well / didn't go well never does.

8. The 4Ls

Four columns: Liked, Learned, Lacked, Longed for. "Learned" is the useful one. It catches things that went badly but taught the team something, which otherwise land in the complaints pile.

9. Starfish

Five columns: keep doing, do more of, do less of, start, stop. It's Start/Stop/Continue with more nuance, because most real changes are "less of" rather than "stop."

For a large group

10. 1-2-4-All

Everyone reflects alone for a minute, then in pairs for two, then fours for four, then each group shares one point with the room. On a call, use breakout rooms. With 12 or more people, open discussion means three people talk and nine listen.

When you have 20 minutes

11. One word plus one question

Each person says one word for the sprint ("crunchy," "foggy," "fine"). Then one question for everyone: "What's one thing we should change next sprint?" Pick one answer, assign an owner, done.

For small teams of three to five, this is often all you need every sprint, with a fuller format once a month.

For the end of the year

12. Year-in-review timeline

A year is too much for went-well / didn't-go-well. Scale up the timeline: each person adds the three moments that mattered most to them, then the team picks two patterns worth carrying into next year.

Run the anonymous question first for this one. "What's one thing about how we worked this year that you'd change?" gets more honest answers before the meeting than during it, especially in the same month as performance reviews.

How do you make a retrospective fun?

Make it short and useful. A retro that ends with one change people can see next sprint beats a themed one that ends with five vague actions.

If the energy is low, open with a two-minute warm-up before the retro starts, not in the middle of it. A quick round of Two Truths and a Lie or a five-question quiz on Truveal Play gets people talking before you ask them to say something critical. Then switch modes clearly: "OK, retro time." For which warm-up suits which meeting, see how to pick the right team game.

If your sprint starts with estimation, the same thinking applies there: simultaneous, unanchored answers. Point Poker handles that half of the sprint.

Frequently asked questions

What are good retrospective ideas for small teams?

For a team of three to five, keep it light: a one-word check-in, a review of last sprint's action items, and one open question about what to change. Small teams talk easily, so elaborate formats add little. The bigger risk is honesty, since there's nowhere to hide on a small team. An anonymous question sent the day before helps people raise the awkward point without being the one who said it.

What are examples of "what went well" in a sprint retrospective?

Good examples are specific enough to repeat: "pairing on the payments bug got it fixed in a day," "we cut scope on Tuesday instead of Friday," or "the new review rotation meant nothing waited more than a day." Vague ones like "good teamwork" give you nothing to keep doing. Ask "what exactly made that work?" until the answer names something concrete.

How often should you change the retrospective format?

Less often than most guides suggest. Keep a format while it produces real action items and people speak up. Change it when the answers get predictable or the same people do all the talking, or roughly once a month to stop it going flat. Keep one part fixed every time: reviewing last sprint's action items. Rotating that out is how retros lose their point.

How long should a sprint retrospective be?

The Scrum Guide caps it at three hours for a one-month sprint and says it's usually shorter for shorter sprints. In practice, 45 to 60 minutes suits a two-week sprint, and 20 to 30 minutes works for a small team using a light format. If yours regularly runs over, the cause is usually too many topics, not too little time. Dot-vote and discuss the top two.