Spice Up Your Retro

Sort your sprint from mild wins to hot issues

Try this retrospective live

Mild

What small wins and steady progress should we call out?

Stand-ups stayed short and on time this sprint, which kept everyone's mornings clear.
The new onboarding doc made it easier for our junior dev to get up to speed.
We hit all our minor deadlines without any last-minute scrambling.
Medium

What added flavor and genuinely worked well?

Pairing on the tricky integration saved us days of debugging.
The mid-sprint demo gave us early feedback that changed our approach for the better.
Cross-team collaboration on the API was smooth and productive.
Hot

What burning issues need urgent attention?

Constant context switching between projects burned a lot of our focus.
The flaky test suite cost us hours of investigation that led nowhere.
Requirements changed midway and we lost momentum re-planning.
Secret Sauce

What bold ideas or experiments should we try next?

Let's try a no-meeting Wednesday to protect focus time.
What if we rotated the facilitator role each sprint to share the load?
We could trial feature flags to ship smaller, safer changes.

What is the Spice Up Your Retro?

Spice Up Your Retro sorts your team's feedback the way you'd rate a dish: by how much heat it carries. Mild items are the small wins nobody mentions. Hot items are the issues that burned the team and need attention now. Between them sit the things that worked, and at the end comes the secret sauce: the ideas you want to try next. The board has four columns. Mild is for small wins and steady progress. Medium covers the practices and decisions that made a real difference. Hot holds the blockers and friction points. Secret Sauce collects bold ideas and experiments for the next sprint. Because the scale runs from good to bad to new, the team covers what went well, what hurt and what to try in one pass. The food theme makes it easier to talk about friction without the conversation getting heavy, and the Mild column makes sure small wins get noticed alongside the big ones. Run it at the end of a sprint or as a quarterly check-in when your usual format has gone stale.

Spice Up Your Retro retrospective format

Mild

What small wins and steady progress should we call out?

Mild is for the low-key positives: small wins, quiet improvements and steady progress that often go unmentioned. Ask the team to call out the little things that made work smoother, even if they seem minor. Progress isn't always dramatic, and this column is where the team notices that.

Medium

What added flavor and genuinely worked well?

Medium is for the practices, collaborations and decisions that made a real difference. Ask what made each one work, so the team knows which habits to keep.

Hot

What burning issues need urgent attention?

Hot covers the blockers, friction points and issues that frustrated people or need attention now. Keep the focus on the situation, not on individuals. The point is to name the burning issues so the team can cool them down with concrete actions.

Secret Sauce

What bold ideas or experiments should we try next?

Secret Sauce is for bold ideas and experiments the team wants to try next. Welcome half-formed suggestions and hold off on judging them while people brainstorm. Pick the best one or two as experiments for the next sprint.

When to use this retrospective

  • When your retrospectives have become routine and the team needs a different format to get talking again.
  • At the end of a sprint, when you want to give wins and pain points equal time.
  • For a team-building session where you want a lighthearted theme that still ends in actions.
  • When quieter team members need a low-pressure structure that makes it easier to contribute.

Suggested icebreaker questions

  • If your week at work was a dish, how spicy would it be and why?
  • What's your go-to comfort food after a tough day, and what made this week tough or easy?

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

Ideas and tips for your retrospective meeting

  • Lean into the spice theme at the start with a quick food question, so people relax before the real discussion.
  • Remind the team to add items to every column, not just Hot.
  • Group similar ideas before voting so the discussion goes to the themes with the most votes.
  • Timebox each column so the team doesn't spend the whole session on the Hot issues.
  • Turn the top Hot items and Secret Sauce ideas into actions with an owner before you close.
  • Rotate the facilitator role so different people get to set the tone.

Frequently asked questions

How long does a Spice Up Your Retro take?
Plan for 45 to 60 minutes with a team of five to eight. To run it faster, give each spice level a few minutes of brainstorming and a few of discussion.
When should I use this retrospective format?
Use it when your usual retros feel stale and the team needs a change. It works at the end of a sprint or as a periodic team-building check-in.
How is it different from a Start, Stop, Continue retro?
Start Stop Continue sorts feedback into actions. Spice Up Your Retro sorts it by intensity: mild wins, medium successes, hot challenges and secret-sauce experiments. It covers similar ground with a lighter theme.
Is this format suitable for remote teams?
Yes. In TeamRetro everyone adds ideas, groups them and votes from wherever they are, at the same time.
How do I make sure the fun theme still produces real outcomes?
Before the session ends, turn the top Hot issues and Secret Sauce ideas into action items, each with an owner. Check on them at the start of your next retro.

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