Use this format when
- The review has strategic and operational dimensions.
- Cross-functional participants need a shared picture.
- The team wants actions visible beside observations.
Retrospective templates Updated
ROBINretrospective template
ROBIN gives complex work five distinct lenses: Risks, Opportunities, Bright Spots, Improvements, and Next Steps. The final column makes the move from observation to commitment visible.
- Duration
- 40–50 minutes
- Team size
- 3–12 people
- Best for
- Strategic reviews, cross-functional projects, and complex delivery periods
What each column means
Use the prompts to keep cards specific. The examples show the level of detail that makes discussion and voting useful.
Risks
3What could reduce the chance of success next?
- The vendor timeline is unconfirmed.
- Knowledge is concentrated in one person.
- Support volume may rise at launch.
Opportunities
3What new advantage or option could the team use?
- Reuse the beta feedback group.
- Automate the new validation rule.
- Pair discovery with support calls.
Bright Spots
3What evidence shows the team or system working well?
- Recovery time fell after the runbook.
- Smaller stories improved flow.
- Design and engineering decided together.
Improvements
3What existing area needs a specific change?
- Clarify ownership before kickoff.
- Test migrations with realistic volume.
- Shorten review waiting time.
Next Steps
3Which actions will the team commit to now?
- Nora confirms the vendor date Friday.
- Sam runs a load test before planning.
- The team reviews ownership at kickoff.
40–50 minutes agenda
A complete path from framing the room to assigning one concrete follow-up.
- 013 minutes
Frame the review
Name the sprint or project being reviewed, restate the purpose of each column, and remind everyone to describe observable events.
- 027 minutes
Write observations silently
Give everyone uninterrupted time to add one specific observation per card across every column.
- 037 minutes
Share and clarify
Read the cards column by column and let authors add context without debating solutions yet.
- 045 minutes
Group and vote
Combine cards that describe the same pattern, then vote for the themes that would most improve the next iteration.
- 0510 minutes
Discuss the leading themes
Explore causes, consequences, and tradeoffs behind the highest-voted themes while making space for dissenting evidence.
- 065 minutes
Commit to one change
Turn the strongest insight into a small action with an owner, deadline, and signal the team can review next time.
Choose another format when
- A short sprint retro needs only three prompts.
- Participants may fill Next Steps before discussing evidence.
- One urgent issue should receive the full meeting.
Facilitation tips
- Keep Risks future-facing and Improvements current.
- Treat Opportunities as options, not mandatory work.
- Use Bright Spots as evidence to preserve strengths.
- Fill Next Steps after voting and discussion.
- Give every next step an owner and review date.
Useful variations
Product ROBIN
Focus risks and opportunities on customer outcomes, evidence, and market timing.
Operational ROBIN
Review reliability, support, deployment, and incident-learning signals.
Portfolio ROBIN
Use the five lenses across connected initiatives and dependencies.
Before the retro
Recommended warm-up
Frequently asked questions
What does ROBIN stand for in a retrospective?
ROBIN stands for Risks, Opportunities, Bright Spots, Improvements, and Next Steps.
When should a team use ROBIN?
Use it for complex or strategic work that needs a broad view and explicit commitments.
How are Risks different from Improvements?
Risks are possible future problems; Improvements are changes to a current practice or condition.
When should the team fill Next Steps?
Fill it after cards are grouped, voted on, and discussed so it contains commitments rather than an unprioritized wish list.
Run this ROBIN Retrospective
Open the ready-made columns, invite the team, collect observations, vote, and leave with an owned improvement.