Strengths, Risks, Learnings Retrospective

A balanced sprint review that looks backward and forward at once — Retromik's signature format.

Use this template free

Free · No credit card · Guests join by link

The board

01

STRENGTHS

What went well this sprint?

02

RISKS

What needs our attention?

03

LEARNINGS

What did we discover?

Strengths, Risks, Learnings is Retromik's default format — a balanced review that captures what to protect (Strengths), what to watch (Risks), and what to carry forward (Learnings) in a single pass.

Unlike purely backward-looking formats, the Risks column points at the next sprint: it collects the dependencies, unknowns, and creeping problems that have not bitten yet. Pairing that with explicit Learnings turns each sprint into compound interest — the team banks what it discovered instead of re-learning it in six months.

When to use Strengths · Risks · Learnings

  • As your default, every-sprint format — balanced enough to never feel wrong
  • Sprint reviews where stakeholders want a risk register, not just team feelings
  • Teams that keep re-solving problems they already solved: the Learnings column is institutional memory
  • When you want one format that works for both calm sprints and rough ones

How to run it in Retromik

  1. 1

    Create cards anonymously

    Everyone adds cards to each column at the same time. In Retromik, cards stay concealed and anonymous while people write, so nobody anchors on the loudest voice.

  2. 2

    Vote on what matters

    Each person places a limited set of voting tokens on the cards they think deserve discussion. Limited tokens force real prioritization.

  3. 3

    Discuss the top cards

    Walk through the highest-voted cards one by one. The facilitator steers the focus; anyone can comment on any card.

  4. 4

    Reveal and group themes

    Authors are revealed and the facilitator drags related cards into named themes, turning scattered notes into patterns.

  5. 5

    Commit to action items

    Convert the discussion into specific, owned action items with due dates — the part most retrospectives skip.

Frequently asked questions

How is this different from 'What went well / What didn't'?

Two ways: Risks looks forward (what could hurt us next) instead of backward (what hurt us), and Learnings captures knowledge explicitly instead of letting it evaporate after the meeting. The result reads like a plan, not a complaint list.

What makes a good Risks card?

Something true today that could hurt tomorrow: 'only one person understands the billing service', 'our staging environment diverges from prod'. If it already caused damage, it is a learning; if it might, it is a risk.

How often should we run this retrospective?

Every sprint. The format is deliberately balanced so it does not wear out with repetition the way emotion-heavy or metaphor-heavy formats can. Many Retromik teams alternate it with Mad, Sad, Glad once a quarter as a morale pulse.

Do participants need an account?

No. The facilitator creates the board and shares a link; teammates join as anonymous guests, add cards, vote, and comment without signing up.

Related templates

Run your next retro with Strengths · Risks · Learnings

Create the board in under a minute, share the link, and your team joins anonymously — no accounts needed for participants.

Start free