How to Run a Sprint Retrospective in Miro (Step-by-Step)
Miro is the most widely used tool for collaborative retrospective facilitation because its infinite whiteboard supports sticky notes, voting, and real-time collaboration in a way that feels natural for both in-person and remote teams. A well-facilitated Miro retro generates more honest input than a video call with no visual surface.
This guide covers setting up a Miro retrospective board, running the session effectively, and capturing action items that stick.
Step-by-step guide
Choose and customize a retro template
In Miro, open the template library (the grid icon) and search "retrospective." Miro offers multiple formats: Start Stop Continue, 4Ls (Liked, Learned, Lacked, Longed For), Mad Sad Glad, and the classic Three Columns. For most agile teams, "Start Stop Continue" provides the clearest action orientation. Duplicate the template to a new board named "Sprint [N] Retrospective [date]."
Set up async pre-work
Share the Miro board link with the team 24 hours before the meeting. Ask each member to add sticky notes to each column anonymously before the session. This async pre-work gives quieter team members equal voice and makes the meeting time more efficient — you spend the session discussing, not brainstorming.
Open the session with data
At the start of the meeting, paste a screenshot of your sprint velocity data (from Jira, Linear, or GitHub) into the top-left of the Miro board. Spend 5 minutes reviewing the sprint facts: completion rate, any blocked tickets, and major wins. This grounds the emotional discussion in objective data.
Cluster and theme the sticky notes
The facilitator (or the group together) spends 10 minutes grouping similar sticky notes by dragging them together. Use the Miro "Frame" tool to draw a box around clusters and label the theme. Common themes that emerge: communication gaps, blocked tickets, unclear requirements, deployment friction.
Run dot voting on priorities
Give each participant 5 votes (use Miro's voting session feature or physical dot stickers in color). Participants vote on the themes they most want to address. The themes with the most votes become the retrospective discussion agenda. This prevents the most vocal team member from dominating the agenda.
Discuss top themes and generate actions
For the 2-3 most-voted themes, run a 10-minute discussion: what caused this, and what specific change would address it? Capture action items on a separate section of the Miro board: action name, owner, and deadline. Action items must be specific and testable — "improve communication" is not an action; "add 5-minute async video update every Monday by 9am" is.
Export actions to your project management tool
Before closing the Miro board, copy all action items to Jira, Linear, or Asana as tickets in the next sprint. Use the Miro sticky note export (right-click > Export as CSV) if you have many items. Miro has native integrations with Jira and Asana for direct issue creation from sticky notes.
Common mistakes
No async pre-work
Starting the retro with blank sticky notes means the first 20 minutes are silent brainstorming. Async pre-work in Miro makes retros significantly more efficient — the meeting time is for discussion, not generation.
Skipping dot voting
Without a prioritization mechanism, the discussion agenda is set by whoever speaks first. Dot voting surfaces what the team collectively considers most important, not what the loudest team member cares about.
Action items left on the Miro board
Miro is where actions are identified; your project management tool is where they live. Actions that stay in Miro get forgotten. Always transfer to Jira/Linear/Asana before the meeting ends.
Tips
Use Miro's timer widget to keep each retrospective section to time
Enable anonymous sticky notes during pre-work to get more honest feedback from quieter team members
Create a Miro board per sprint and keep them in a dedicated Miro project folder for historical reference
Use the Miro + Jira integration to create Jira issues directly from sticky notes via right-click
How Vantage helps
Vantage captures the context behind product decisions so retrospective discussions can go beyond "why did this take so long" to "was the PRD clear enough for engineering." When retrospectives reveal requirement clarity issues, Vantage makes it easy to improve the next PRD generation.