Running a retrospective in Figma gives your team a visual, interactive space to reflect on past work and plan improvements. Unlike scattered documents or generic survey tools, Figma keeps everyone focused, enables live collaboration, and creates a permanent record you can reference later.
Why Figma
Figma excels at retrospectives because it combines real-time collaboration with visual organization. Your entire team works in one shared space, watching ideas appear instantly without lag or version conflicts. You can create sections for different retrospective categories (what went well, what didn't, action items), use color coding for priorities, and build templates you reuse each sprint.
Beyond the technical advantages, Figma removes friction from the retrospective process. Team members can contribute anonymously through comments before the meeting, reducing groupthink. Designers, engineers, and product managers use Figma daily, so there's no learning curve. You can screenshot outcomes, share them in Slack, and embed them in product docs. For distributed teams, Figma's integrated video calls mean you're not toggling between platforms.
Step-by-Step Guide
1. Create a Retrospective Template File
Start in your Figma workspace and create a new file titled "Sprint [number] Retrospective" or use a consistent naming convention like "Retro_2025_Q1_Week2". This makes archived retros searchable.
Open Figma and navigate to your team workspace. Click "New file" in the top left. Name it with your sprint identifier. Once created, you'll work from a blank canvas. Set up your page by clicking on the current page name (usually "Page 1") and renaming it to "Retrospective" for clarity.
Before the meeting, add a title frame at the top of your canvas. Use the text tool (keyboard shortcut T) and type "Sprint [X] Retrospective" in a large font size (32-48pt works well). Below this, add the sprint dates and team name. This sets context immediately when people join.
2. Create Four Core Sections
Design four separate frames on your canvas to organize feedback categories: "What Went Well," "What Could Improve," "Blockers," and "Action Items." These sections map to traditional retrospective formats while staying flexible.
Start by creating the first frame. Click the "Frame" tool in the left toolbar (keyboard shortcut F). Drag to create a large rectangular frame on the left side of your canvas. Label it "What Went Well" using the text tool. Use a green color for the stroke (outline) to visually code this positive category. Set the frame dimensions to approximately 400x500 pixels for ample writing space.
Duplicate this frame three times by selecting it and pressing Ctrl+D (or Cmd+D on Mac). Rename the duplicated frames "What Could Improve," "Blockers," and "Action Items." Change the stroke colors to orange, red, and blue respectively. This color coding helps team members scan the canvas quickly. Space these frames evenly across your canvas, leaving about 50 pixels between each to avoid cramping.
Inside each frame, add placeholder text that says "Click to add comment" or similar. This guides team members on how to participate. You can delete this text once contributions start flowing.
3. Distribute the File and Enable Comments
Share your retrospective file with all attendees 24 hours before the meeting. This gives asynchronous contributors time to add thoughts without meeting pressure.
Click the "Share" button in the top right of your Figma window. Select "Edit" from the permission dropdown (not "View," since you want participants to add content). Copy the link and send it via email or Slack with clear instructions: "Please add your thoughts to the appropriate sections before our retro meeting tomorrow at 2pm."
Configure Figma's commenting settings to encourage participation. Participants can click the "+" next to any frame and add comments. For anonymous contributions, you can create a separate "Anonymous Feedback" frame where people paste thoughts they want untethered from their name. Some PMs ask team members to comment first, then discuss live during the meeting.
Before sharing, test the link yourself in an incognito browser to ensure permissions work correctly. Nothing derails a retro faster than access issues.
4. Facilitate Live Discussion During the Meeting
Schedule your retrospective meeting at the set time with all participants opening the Figma file. Ask someone to screen-share their view to the group. This ensures everyone sees the same canvas, regardless of their individual zoom levels or screen sizes.
Start with "What Went Well" and read comments aloud, clustering similar themes. Use Figma's text tool to add summary labels like "Strong Communication" or "Fast Shipping" directly on the frame. This synthesis helps the team see patterns. For each comment thread, spend 2-3 minutes discussing before moving to the next section.
When you reach "What Could Improve," set a norm that criticism is structural, not personal. Rephrase comments neutrally if needed ("We could improve deployment speed" instead of "Engineering was slow"). Record themes the same way as the positive section.
Use the "Blockers" section to identify systemic obstacles. These often feed directly into action items. If someone mentions "unclear requirements," note it here, then later turn it into an action item like "PM to provide requirements template by next sprint."
5. Populate Action Items with Ownership
Move to your "Action Items" frame and create a structured list. For each action item, use text to note what needs doing, who owns it, and when it's due. Format each entry like this: "[Owner] will [action] by [date]."
You can also add a simple table directly in Figma for more structure. Use the shape tool to create columns for "Action," "Owner," and "Due Date." While Figma isn't a spreadsheet, this lightweight approach keeps everything in one file. Alternatively, create a frame that links to a tool for tracking action items where you'll add formal accountability later.
For ownership, ask team members directly: "Who's committing to researching better QA processes?" Never assign actions without the person's verbal agreement. Write their name and get them to acknowledge. This prevents action items from becoming ghost tasks.
6. Capture Metrics or Velocity Notes
Add a frame titled "Metrics" or "Velocity" at the bottom of your canvas where you record sprint performance data. Include lines like "Planned story points: X," "Completed story points: Y," "Bugs found in QA: Z," and "Customer support tickets: W."
This contextualizes your retro. If you shipped 120 points and planned 100, that's a success to celebrate in "What Went Well." If bugs doubled from last sprint, it explains team frustration captured in "What Could Improve." Reference your project management tool (Jira, Linear, or similar) to pull accurate numbers. Add this data before the meeting so the team sees it upfront.
You can pull these numbers from your PM tools directory integration if your sprint tracking tool syncs with Figma, or simply copy-paste them into a text frame.
7. Document the Discussion in Real Time
As the facilitator, add a "Notes" frame where you capture nuance that pure comments don't convey. If the team discusses why a blockers emerged, jot it down. These notes become gold when you review past retros looking for patterns.
Click to add text in your Notes frame and type summary sentences as conversation happens. For example: "Deployment delays traced to manual testing bottleneck. Team agreed to prioritize test automation next sprint." Keep sentences short and specific. This frame is your safety net if someone later asks "Why did we decide to do X?"
8. Share and Archive Outcomes
After the meeting, create a summary document or Slack message with key takeaways. Screenshot the completed Figma file, focusing on each section. Use Figma's built-in "Share prototype" feature (top right menu) to generate a read-only link for stakeholders who didn't attend.
Move the file into a "Retrospectives Archive" folder in your Figma workspace. Name it with the sprint or date so you can retrieve it later. Many PMs create a master file that links to all past retros, making it easy to search for historical decisions.
Send a follow-up message reiterating action items, owners, and dates. Reference the Figma link so anyone can review the full discussion. This transparency builds accountability and ensures nothing gets lost.
Pro Tips
- Create a reusable template by duplicating your first retro and clearing content each sprint. This saves setup time and maintains consistency across retrospectives.
- Use Figma's color highlighting feature to mark action items by status during follow-up retros. Green for completed, yellow for in-progress, red for blocked. This shows momentum and accountability.
- Enable video comments in Figma (available on paid plans) so team members can record short voice clips explaining complex feedback. This adds nuance that text sometimes misses.
- Assign someone as "scribe" to manage comments during the live meeting, clustering similar feedback in real time. This prevents duplication and keeps the canvas organized.
- Link your Figma retro file in your guide on agile product management or knowledge base so new team members see your retrospective culture.
When to Upgrade to a Dedicated Tool
Figma works perfectly for small to mid-sized teams (5-20 people) running retros once or twice per sprint. It shines when your team already uses Figma daily and values visual collaboration.
Consider moving to a dedicated retrospective tool if your organization has 50+ people running simultaneous retros, requires anonymous voting on action item priority, or needs automated follow-up workflows that trigger reminders about past action items. Tools like RetroTool or TeamRetro integrate with Slack and include features like "What did we learn?" tracking across quarters. If you run retros across multiple time zones and need asynchronous voting features, compare your options with a formal review.
For most product teams, though, Figma eliminates tool bloat. It's free or low-cost if you already have seats, requires zero training, and integrates with your existing Slack and email workflows.