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

STRENGTHS

What went well this sprint?

RISKS

What needs our attention?

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 a Strengths, Risks, Learnings Retrospective

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 a Strengths, Risks, Learnings Retrospective

1
Write risks as if-then
A good risk card says what could happen and what it would cause: "If the vendor delays the API again, we miss the launch date." That makes it easy to judge how serious it is.
2
Protect strengths by name
For the top Strength cards, ask what made them work. A strength the team can explain is one it can keep.
3
Turn learnings into rules of thumb
Rewrite strong Learning cards as something the team will do from now on: "split stories under three points".
4
Give every top risk an owner
Vote, discuss, then leave with an owner and a first step for each of the top one or two risks.

Anonymous writing, voting, grouping and action items work the same as in any Retromik retro.

Read the full facilitation guide

Example cards

What good cards look like for a software team. Specific, about the work, never about a person.

STRENGTHS

Releases went out every day without an incident.
Design reviews caught two usability issues early.

RISKS

If the vendor delays the API again, we miss the launch date.
If Ali is out, nobody can approve database changes.

LEARNINGS

Stories under three points made the sprint more predictable.
Asking Support before building saved us a round of rework.

A 45-minute agenda

0–5 minSet the scope: this sprint and the next
5–15 minWrite cards silently
15–20 minVote, three votes each
20–35 minDiscuss the top risks, then strengths and learnings
35–45 minOwners for the top risks; learnings turned into team rules

Common mistakes

Risks that describe the past. If it already happened, it's a learning.
Learnings so obvious nobody will change anything because of them.
Risks discussed but left without an owner.
Skipping strengths because the risks feel more urgent.

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.

Why is Strengths, Risks, Learnings a good default?

It covers the past, the future and what to carry forward in one pass, without a metaphor to explain. That makes it a safe choice for any sprint and for teams new to retros. Switch formats every few sprints to keep it fresh.