How to Run Your First Retrospective: A Step-by-Step Guide
April 16, 2025
RetroFlow Team
The RetroFlow team builds free retrospective tools and writes practical guides for agile teams. We have helped thousands of teams run better retros.
Running your first retrospective can feel daunting. This guide walks you through everything—from preparation to follow-up—so your first retro is effective and sets the foundation for continuous improvement.
Before the Retrospective
1. Schedule the Meeting
Timing:
- 60 minutes for first retrospective
- End of sprint, project phase, or month
- When team is available and fresh
- Avoid Mondays and Fridays if possible
Invite:
- All team members who worked together
- Optional: Manager (consider if it affects openness)
- Keep it focused (5-8 people ideal)
2. Choose Your Format
For your first retro, use Start-Stop-Continue:
| Category | Question |
|---|---|
| Start | What should we begin doing? |
| Stop | What should we stop doing? |
| Continue | What’s working that we should keep? |
Why this format:
- Easy to understand
- Action-oriented
- Familiar concepts
- Quick to explain
3. Set Up Your Tool
Using RetroFlow:
- Go to RetroFlow
- Create new retrospective
- Select Start-Stop-Continue format
- Copy the share link
Share the link before the meeting so everyone can access it.
4. Prepare Your Facilitation Notes
Agenda:
- Welcome & set expectations (5 min)
- Silent brainstorming (10 min)
- Voting (3 min)
- Discussion (30 min)
- Action items (10 min)
- Close (2 min)
Key phrases to remember:
- “This is about improving, not blaming”
- “All perspectives matter”
- “Let’s focus on what we can control”
Running the Retrospective
Phase 1: Welcome & Set Expectations (5 min)
Start with the purpose:
“We’re here to reflect on [time period] and identify ways to improve. This isn’t about blame—we’re all on the same team trying to get better.”
Introduce the Prime Directive:
“Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.”
Explain the format:
“We’ll use Start-Stop-Continue. Think about:
- START: Things we should begin doing
- STOP: Things we should stop doing
- CONTINUE: Things that are working well”
Set ground rules:
- Speak from your own experience (“I felt…” not “You always…”)
- One conversation at a time
- What’s said here stays here
- All input is valid
Phase 2: Silent Brainstorming (10 min)
Instructions:
“Take 10 minutes to add your thoughts to each column. Don’t worry about duplicates—we’ll group them later. Write as many items as you want.”
Facilitator actions:
- Start the timer
- Add your own items (model participation)
- Remind at 5 minutes and 2 minutes
- Stay silent—let people think
Tips:
- Anonymous mode helps people be honest
- Silence is productive—don’t fill it
- If someone finishes early, encourage more items
Phase 3: Voting (3 min)
Instructions:
“Everyone gets 5 votes. Vote for the items you think are most important to discuss. You can put multiple votes on one item if it’s really important to you.”
Facilitator actions:
- Start voting round
- Wait for everyone to finish
- Sort by votes when done
Phase 4: Discussion (30 min)
Start with highest-voted items:
“Let’s start with [top-voted item]. Who added this? Tell us more about what you meant.”
For each item:
- Clarify: “Can you explain what you mean?”
- Expand: “Does anyone else have thoughts on this?”
- Root cause: “Why do you think this happened?”
- Action: “What could we do about this?”
Time management:
- Aim for 5-7 minutes per item
- Cover top 4-6 items
- Don’t try to solve everything
- Note items for future retros
Facilitation techniques:
If someone dominates:
“Thanks for that perspective. Let’s hear from others too.”
If silence:
“I’ll give everyone a moment to think…” “What do others observe about this?”
If going off-topic:
“That’s a good point. Let’s note it and come back to our main topic.”
If getting heated:
“I can see this is important. Let’s focus on what we can do going forward.”
Phase 5: Action Items (10 min)
Transition:
“Let’s turn our discussion into concrete actions. What specific things will we do differently?”
Good action items have:
- Specific: Clear what needs to happen
- Owner: One person responsible
- Deadline: When it will be done
- Achievable: Can be done before next retro
Examples:
❌ Vague: “Improve communication” ✅ Specific: “Alex will send weekly status update every Friday”
❌ No owner: “Update the documentation” ✅ With owner: “Jordan will update onboarding docs by next Wednesday”
❌ Too big: “Fix all the technical debt” ✅ Achievable: “Sam will refactor the login module this sprint”
Aim for 2-4 action items:
- Better to complete a few than start many
- Can always add more next retro
- Focus on highest impact
Phase 6: Close (2 min)
Summarize:
“Great retro! We discussed [key topics] and committed to [action items].”
Thank the team:
“Thanks everyone for your openness. This helps us improve.”
Set expectations:
“We’ll check in on these actions at our next retro.”
Optional: Quick feedback:
“One word—how was this retro for you?”
📖 Explore more: sprint retrospective questions
After the Retrospective
Immediately After
Document results:
- Export or screenshot the board
- List action items with owners and dates
- Share summary with team
Sample summary email:
Subject: Retrospective Summary - [Date]
Team,
Thanks for a great retrospective! Here's what we covered:
KEY THEMES:
• [Theme 1]
• [Theme 2]
• [Theme 3]
ACTION ITEMS:
1. [Action] - Owner: [Name] - Due: [Date]
2. [Action] - Owner: [Name] - Due: [Date]
3. [Action] - Owner: [Name] - Due: [Date]
We'll review progress at our next retrospective.
Thanks!
During the Next Period
Track action items:
- Check in during standups
- Offer help if blocked
- Celebrate completions
Note new items:
- Keep a running list for next retro
- Capture feedback as it happens
- Don’t wait until the retro
At Next Retrospective
Start by reviewing actions:
- What was completed?
- What’s still in progress?
- What got blocked?
Celebrate progress:
- Acknowledge completed items
- Recognize improvements
- Build momentum
Common First-Time Challenges
Challenge: People Don’t Speak Up
Causes:
- Not feeling safe
- Unsure what’s expected
- Dominant personalities
Solutions:
- Use anonymous mode
- Start with written input before discussion
- Directly invite quiet people: “What do you think?”
- Create smaller breakout discussions
Challenge: Only Negative Feedback
Causes:
- Pent-up frustration
- Need to vent
- Format doesn’t prompt positives
Solutions:
- Explicitly ask for positives in Continue/Liked
- Acknowledge the negatives
- Balance with “What’s working?”
- Consider if issues need addressing outside retro
Challenge: Discussion Goes Off-Track
Causes:
- Related topics emerge
- No time limits
- Avoiding hard topics
Solutions:
- Use a “parking lot” for side topics
- Time-box discussions
- Gently redirect: “Let’s save that for later”
- Stay focused on actionable items
Challenge: No Action Items
Causes:
- Discussion without closure
- Items too vague
- No accountability
Solutions:
- Explicitly ask “What will we do about this?”
- Require owner and deadline
- Keep actions small and specific
- Follow up at next retro
Challenge: Same Issues Every Time
Causes:
- Actions not completed
- Root causes not addressed
- Issues outside team control
Solutions:
- Review action completion rigorously
- Dig deeper into root causes
- Escalate systemic issues
- Focus on what team can control
Tips for Your First Facilitation
Do:
- ✅ Prepare: Know the format and agenda
- ✅ Participate: Add your own items
- ✅ Listen: Let team do most talking
- ✅ Time-box: Keep discussion moving
- ✅ Summarize: Repeat key points
- ✅ Follow up: Track actions
Don’t:
- ❌ Lecture: This is about the team, not you
- ❌ Judge: Accept all input without reaction
- ❌ Dominate: Ask questions, don’t answer them
- ❌ Rush: Allow silence and thinking
- ❌ Over-complicate: Start simple
- ❌ Skip follow-up: Actions matter most
Recovery Phrases
If you lose track:
“Let me take a moment to collect my thoughts…”
If discussion stalls:
“What else haven’t we touched on?”
If running out of time:
“We’ve [X] minutes left. Let’s focus on actions.”
If emotions run high:
“I hear this is important. Let’s make sure we capture an action for it.”
These questions work especially well with structured formats. Browse 30+ retrospective formats to find the right match.
Quick Reference: 60-Minute Agenda
| Phase | Time | Activity |
|---|---|---|
| Welcome | 5 min | Purpose, Prime Directive, format |
| Brainstorm | 10 min | Silent writing |
| Voting | 3 min | Prioritize items |
| Discussion | 30 min | Talk through top items |
| Actions | 10 min | Create commitments |
| Close | 2 min | Summary, thanks |
What Success Looks Like
After Your First Retro:
- Team participated
- Some honest feedback surfaced
- 2-3 action items created
- People felt heard
After a Few Retros:
- Participation increases
- Deeper issues discussed
- Actions getting completed
- Visible improvements
Over Time:
- Retrospectives become valued
- Continuous improvement culture
- Trust and openness grow
- Team performs better
Ready to Start?
Your first retrospective doesn’t need to be perfect. It needs to happen. Start simple, learn from it, and improve your retrospectives just like you improve your work.
Run First with RetroFlow
Most retro tools charge per user or cap free boards at 3. RetroFlow doesn’t — every feature is free, no account needed. Share a link and your team starts contributing in seconds.
Related Resources
- Retrospective Questions for New Teams
- using retros outside of agile teams
- How To Facilitate Retrospective
- What Is a Sprint Retrospective? - Fundamentals
- Retrospective Facilitation Tips - Better facilitation
- 50 Retrospective Questions - Questions to ask