Running Effective Retrospectives

Retrospectives are the engine of continuous improvement. Good retrospectives surface honest feedback, identify patterns, and produce changes that actually happen. Poor retrospectives waste time and breed cynicism. This guide covers facilitation techniques that make retrospectives valuable.

Retrospective Structure

Preparation

Before the Retro

RETROSPECTIVE PREP
══════════════════

FACILITATOR PREP:
─────────────────────────────────────
Before the meeting:
├── Review previous action items
├── Check sprint data (velocity, bugs)
├── Note significant events
├── Choose retro format
├── Prepare materials (board, prompts)
└── 15 min prep improves quality

SHARE CONTEXT:
─────────────────────────────────────
Send reminder with:
├── Time and link
├── Previous action item status
├── Sprint summary data
├── Format we'll use
├── Ask to reflect beforehand
└── People come prepared

PREVIOUS ACTIONS:
─────────────────────────────────────
Always start by reviewing:
├── What did we commit to last time?
├── Did we do it?
├── If not, why not?
├── Accountability matters
└── Builds trust in process

Formats

Popular Approaches

RETRO FORMAT OPTIONS
════════════════════

CLASSIC: WHAT WENT WELL / IMPROVE / ACTIONS
─────────────────────────────────────
Columns:
├── 😊 What went well
├── 😕 What could improve
├── 💡 Actions
└── Simple, versatile

Process:
1. Everyone adds stickies (5 min)
2. Group similar items (3 min)
3. Vote on priorities (2 min)
4. Discuss top items (10 min)
5. Define actions (5 min)

START/STOP/CONTINUE:
─────────────────────────────────────
Columns:
├── 🟢 Start doing
├── 🔴 Stop doing
├── 🟡 Continue doing
└── Action-oriented

4 Ls: LIKED/LEARNED/LACKED/LONGED FOR:
─────────────────────────────────────
Categories:
├── 💚 Liked (positive)
├── 🧠 Learned (insights)
├── ❌ Lacked (missing)
├── 💭 Longed for (wished we had)
└── More nuanced reflection

SAILBOAT:
─────────────────────────────────────
Visual metaphor:
├── ⛵ Boat: Team/project
├── 💨 Wind: What propels us
├── ⚓ Anchor: What holds us back
├── 🪨 Rocks: Risks ahead
├── 🏝️ Island: Goal/destination
└── Engaging, different perspective

Facilitation

Running the Session

FACILITATION TECHNIQUES
═══════════════════════

SET THE STAGE:
─────────────────────────────────────
Check-in:
├── Brief mood check
├── "One word for the sprint?"
├── Temperature check
├── Get everyone talking early
└── 5 minutes max

Safety reminder:
"What's said here stays here.
No blame. We're here to learn."

GATHER DATA:
─────────────────────────────────────
Silent brainstorming:
├── Everyone writes ideas (5 min)
├── One idea per sticky/card
├── No discussion yet
├── All perspectives captured
├── Quieter voices contribute
└── Then share and group

Group similar items:
├── Read aloud and cluster
├── Name the themes
├── Creates discussion topics
└── Quick affinity mapping

VOTE:
─────────────────────────────────────
Dot voting:
├── Each person gets 3 votes
├── Vote on what to discuss
├── Top items get discussed
├── Prioritize limited time
└── Democratic selection

DISCUSS TOP ITEMS:
─────────────────────────────────────
For each priority:
├── What happened?
├── Why did it happen?
├── What's the root cause?
├── What could we do differently?
└── Dig deeper than symptoms

DEFINE ACTIONS:
─────────────────────────────────────
For each insight:
├── What specifically will we do?
├── Who will own it?
├── When will it happen?
├── How will we verify?
└── Concrete, not vague

Creating Safety

PSYCHOLOGICAL SAFETY
════════════════════

SAFE ENVIRONMENT:
─────────────────────────────────────
People must feel safe to:
├── Share concerns
├── Admit mistakes
├── Challenge decisions
├── Disagree respectfully
├── Raise uncomfortable topics
└── Without fear of repercussion

FACILITATOR ROLE:
─────────────────────────────────────
Create safety by:
├── Set ground rules
├── Protect all voices
├── Shut down blame
├── Thank people for sharing
├── Keep confidential
└── Model vulnerability

ANONYMOUS INPUT:
─────────────────────────────────────
When needed:
├── Anonymous submission before meeting
├── Written before verbal
├── Private channels for concerns
├── Facilitation by neutral party
├── If manager is problem, separate session
└── Safety over formality

MANAGER BEHAVIOR:
─────────────────────────────────────
If manager in room:
├── Speak last
├── Listen more than talk
├── Accept feedback gracefully
├── Don't defend or explain
├── Thank for honesty
└── Actions speak louder

Actions

Making Change Happen

EFFECTIVE ACTIONS
═════════════════

ACTION CRITERIA:
─────────────────────────────────────
Good action:
├── Specific (not vague)
├── Measurable (know when done)
├── Owned (one person accountable)
├── Time-bound (by when)
├── Achievable (can actually do)
└── SMART-ish

Examples:

❌ Vague:
"Improve communication"

✅ Specific:
"Sarah will set up daily 5-min standup
in Slack by end of week"

LIMIT ACTIONS:
─────────────────────────────────────
Pick 1-2 improvements per sprint.
Not 10.

Why:
├── Focus increases completion
├── Too many = none done
├── Build momentum with wins
├── Compound over time
└── Less is more

TRACK COMPLETION:
─────────────────────────────────────
Every retro starts with:
├── "Last time we committed to X"
├── "Did we do it?"
├── "If not, why?"
├── Accountability
└── Builds trust in process

If actions never complete:
├── They're too big → Make smaller
├── No ownership → Assign clearly
├── Forgotten → Put in sprint backlog
├── Process issue → Address meta-problem
└── Don't give up on improvement

Remote Retrospectives

Distributed Teams

REMOTE RETRO TIPS
═════════════════

TOOLS:
─────────────────────────────────────
Online whiteboard:
├── Miro
├── FigJam
├── Notion
├── GitScrum boards
└── Visual collaboration

Video:
├── Cameras on
├── Good audio
├── Gallery view
├── See reactions
└── More engaging

ADAPTATIONS:
─────────────────────────────────────
Time for async:
├── Add stickies before meeting
├── Vote asynchronously
├── Meeting is discussion
├── Respects timezones
└── Prep increases quality

Engagement:
├── Call on people by name
├── Use reactions/emojis
├── Chat for side thoughts
├── More structured facilitation
├── Check in on quiet folks
└── Remote needs more intention

FOLLOW UP:
─────────────────────────────────────
After meeting:
├── Share summary in writing
├── Actions in project tool
├── Accessible to all
└── Written record

GitScrum Retrospectives

Integration

GITSCRUM FOR RETROS
═══════════════════

SPRINT SUMMARY:
─────────────────────────────────────
Auto-generated:
├── What was completed
├── What carried over
├── Velocity
├── Blockers faced
├── Context for discussion
└── Data-driven retro

ACTION ITEMS:
─────────────────────────────────────
Create tasks for actions:
├── Retro action as task
├── Assigned owner
├── Due date
├── In sprint backlog
├── Tracked like other work
└── Gets done

HISTORICAL VIEW:
─────────────────────────────────────
Past retros:
├── What we committed to
├── What we completed
├── Patterns over time
├── Progress visible
└── Learning documented

Best Practices

For Retrospectives

1. Psychological safety first — Honest input requires trust
2. Start with previous actions — Accountability builds credibility
3. Limit actions to 1-2 — Focus increases completion
4. Vary formats — Prevent staleness
5. Follow through — Actions must actually happen

Anti-Patterns

RETRO MISTAKES:
✗ Nothing ever changes
✗ Blame culture
✗ Same issues every time
✗ Manager dominates
✗ No action items
✗ Too many action items
✗ No follow-up
✗ Skipping retros "too busy"

Related Solutions

• Building high-performing teams
• Team communication best practices
• Sprint review best practices