Use this format when
- Participation has become uneven.
- A reorganization or incident changed team confidence.
- Important concerns arrive only after decisions.
Retrospective templates Updated
Safety Checkretrospective template
A Safety Check retrospective looks at the conditions around candor and participation. It helps a facilitator discuss hesitation without asking people to expose more than they choose.
- Duration
- 30–40 minutes
- Team size
- 3–12 people
- Best for
- Low participation, recent team change, and rebuilding psychological safety
What each column means
Use the prompts to keep cards specific. The examples show the level of detail that makes discussion and voting useful.
What Felt Safe
3Where could people ask, challenge, admit, or contribute confidently?
- Pairing made it easy to ask basic questions.
- The incident review separated learning from blame.
- Product welcomed disagreement during discovery.
Where We Hesitated
3Where did people hold back, wait, or avoid raising a concern?
- We noticed the deadline risk but waited to say it.
- Junior reviewers rarely challenged the design.
- Nobody questioned the handoff during the meeting.
Support We Need
3What agreement, behavior, or resource would increase confidence next?
- Invite written dissent before decisions close.
- Let the incident facilitator speak last.
- Clarify who can stop a risky release.
30–40 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
- The facilitator cannot protect confidentiality.
- A formal misconduct issue needs the proper organizational process.
- Leadership wants to identify who wrote critical feedback.
Facilitation tips
- Offer anonymous cards.
- Let people pass without explanation.
- Discuss conditions and behaviors, not personalities.
- Do not promise confidentiality the tool or setting cannot provide.
- Choose an action leaders are prepared to honor.
Useful variations
Anonymous safety check
Hide authors and collect cards before discussion to reduce social pressure.
Decision safety check
Focus on who spoke, challenged, and understood a recent important decision.
New-team check
Use the prompts to shape working agreements during a team formation or reorganization.
Before the retro
Recommended warm-up
Frequently asked questions
What is a Safety Check retrospective?
It is a retrospective focused on conditions that support or inhibit speaking up, asking for help, and challenging decisions.
Should Safety Check cards be anonymous?
Anonymous writing can help when confidence is low, but the facilitator must state clearly how anonymity works and avoid trying to identify authors.
Is this a psychological safety assessment?
No. It is a facilitated team conversation, not a clinical, HR, or validated organizational assessment.
What action should follow the retro?
Choose one observable change, such as written dissent before decisions or a clear right to stop risky releases.
Run this Safety Check Retrospective
Open the ready-made columns, invite the team, collect observations, vote, and leave with an owned improvement.