Templates/Stoplight
Leadership, Remote Teams, Continuous Improvement, Fun

Stoplight Retrospective Template

An intuitive traffic-light retro format — Red for blockers, Yellow for caution, Green for smooth sailing — that makes team health instantly visible at a glance.

10–20 min3 columnsRemote friendly
Create a board
Stoplight template illustration
Interactive preview

See it in action

Drag example cards between columns or try voting to explore the format.

9 example cards · changes stay in this previewDrag cards between columns

Red3

Stop — what's blocking the team? Critical issues that need immediate attention.

Prod database hitting connection limits — needs immediate scaling

Third-party API deprecation — migration not started

Team is one person short critical path

Yellow3

Caution — what needs monitoring? Issues that aren't critical yet but could become Red.

Documentation is falling behind feature development

Test coverage dropped below 60% this sprint

On-call rotation is burning out the senior engineers

Green3

Go — what's working well? Practices, tools, and behaviors to maintain.

CI pipeline is fast and reliable

Design-review collaboration is excellent

Sprint planning is well-organized and focused

The prompts behind the format

What goes in each column?

Use these prompts and example cards to start a focused conversation.

Red

Stop — what's blocking the team? Critical issues that need immediate attention.

Example cards

  • Production database is at capacity
  • Key dependency is blocked waiting for another team
  • Team member is out with no backup plan

Keep in mind: Don't list minor annoyances as Red — Yellow exists for that

Yellow

Caution — what needs monitoring? Issues that aren't critical yet but could become Red.

Example cards

  • Test coverage is declining sprint over sprint
  • Communication with stakeholders could be better
  • Technical debt in the payment module is growing

Keep in mind: Don't let Yellow items become chronic — if it's Yellow for 3 sprints, it's really Red

Green

Go — what's working well? Practices, tools, and behaviors to maintain.

Example cards

  • Deployment pipeline is stable
  • Team collaboration has never been better
  • New agile process is working well

Keep in mind: Don't skip Green — it's essential for balance

Timeline

How to run it

Stoplight takes about 10–20 min. Here's the flow.

2
01

Explain

Red = blockers, Yellow = caution/warning, Green = smooth sailing. Blameless and honest.

5
02

Add cards

Team adds cards to all three columns. Encourage at least one card per column.

5
03

Vote and group

Vote on items. Reds get priority attention — discuss how to unblock.

5
04

Action planning

Focus actions on Reds and Yellows. Greens are good — protect them.

3
05

Close

Share a quick summary. If many Reds, schedule a dedicated problem-solving session.

Best practices
  • ✓Treat Red items as must-fix before the next sprint — assign ownership immediately.
  • ✓Track the Red/Yellow/Green distribution over time — a trend toward more Red is an escalation signal.
  • ✓Give Yellow items deadlines — a Yellow that isn't addressed becomes a Red.
  • ✓Celebrate Green items publicly — they're proof that improvement efforts work.
  • ✓Use emoji reactions for quick voting if you're running async.
  • ✓Pair Stoplight with a deeper format monthly — it's a diagnostic, not a therapy session.
Common mistakes
  • ✗Treating Yellow as 'not important' — Yellow items are early warning signals.
  • ✗Taking Green for granted — what made this sprint green? Protect those practices.
  • ✗Allowing Reds to repeat sprint after sprint — escalate recurring Reds to leadership.
  • ✗Running Stoplight as the only retro format — it lacks depth for complex issues.
  • ✗Letting team members overuse Red for minor issues — Yellow exists for noise.
  • ✗Not assigning owners to Red items before the retro ends.
About this template

What is a Stoplight retrospective?

The Stoplight retrospective (also known as Red, Yellow, Green) uses one of the most universally understood visual metaphors: a traffic light. Red means stop — what's blocking the team? Yellow means caution — what needs attention? Green means go — what's working well?

This format's brilliance lies in its intuitive visual nature. Every team member instinctively understands the traffic light metaphor, which means zero onboarding time and immediate participation. The format originated in Lean management and Just-in-Time manufacturing, where shop floor teams used red/yellow/green indicators to signal production line health. It was adapted for Agile retrospectives by facilitators who needed a format that could surface team health signals at a glance.

The psychological advantage of Stoplight is its non-confrontational nature. Team members can signal distress (Red) or concern (Yellow) without having to articulate detailed complaints. For teams with introverted members or power distance dynamics, this low-friction signaling is invaluable. A Red card might just say "API stability" — the team knows what that means without forcing the author to elaborate publicly.

FAQ

Frequently asked questions

What is a Stoplight retrospective?

Stoplight (Red, Yellow, Green) uses a traffic light metaphor. Red is blockers, Yellow is caution, Green is what's working. It provides an instant visual health check for any team.

How long does a Stoplight retro take?

10–20 minutes. It's one of the fastest formats because the metaphor is immediately understood.

Is Stoplight good for leadership teams?

Yes — leadership teams benefit from the instant visual health check. A board full of Red is an immediate escalation signal.

Can I run Stoplight for remote teams?

Yes — the traffic light metaphor is universal and requires no special context. LetRetro's board makes Red/Yellow/Green signals visible at a glance.

How do I track Red/Yellow/Green over time?

LetRetro automatically tracks column distribution across sprints, giving you a team health trend line.

What if everything is Green?

Celebrate! But also ask: are we being honest? If multiple sprints are all Green, the team may be avoiding difficult conversations.

Run your stoplight retrospective

Free forever plan. Start running better retrospectives in under 2 minutes.

Get Started Free