Excel remains one of the most practical tools for running retrospectives, especially for product managers working with distributed teams or operating in resource-constrained environments. The familiarity of spreadsheets eliminates adoption friction, real-time collaboration features enable synchronous participation, and the flexibility of columns and formulas lets you customize the format to your team's specific needs.
Why Excel
Excel works particularly well for retrospectives because nearly every team member already has access to it and knows how to use it. Unlike specialized retro tools that require onboarding and licensing, Excel files can be shared instantly through email or cloud storage, and participants can start contributing immediately without learning a new interface. The spreadsheet format naturally structures feedback into categories, makes it easy to sort and filter themes, and provides built-in functionality for voting, timing, and analysis that would otherwise require multiple tools.
Beyond accessibility, Excel's collaboration features through Microsoft 365 or Google Sheets enable real-time editing where multiple people can input thoughts simultaneously. This asynchronous-first approach works well for teams across time zones, where not everyone can attend a live meeting. The data remains organized in one place, making it simple to reference previous retrospectives, track action items over time, and identify recurring patterns in team feedback.
Step-by-Step Guide
1. Create Your Retrospective Template
Start by opening a new blank spreadsheet in Excel or Google Sheets. Create your first worksheet tab and name it with the sprint or release date (for example, "Retro-Sprint-47" or "Q1-Product-Launch"). In the first row, add the following column headers:
- Column A: "Category"
- Column B: "Feedback"
- Column C: "Owner"
- Column D: "Votes"
- Column E: "Action Item"
- Column F: "Status"
Under the Category column, add the standard retrospective sections in rows 2-4: "Went Well" in A2, "Needs Improvement" in A3, and "Action Items" in A4. Leave plenty of blank rows under each category (suggest 10-15 rows per section) to accommodate participant input. You can adjust these categories based on your team's preferences. Some teams use "Start, Stop, Continue" or "Rose, Thorn, Bud" instead. Whatever structure you choose, keep it consistent across retrospectives for easier analysis.
Format your header row by selecting row 1, then apply bold text through the Home menu (keyboard shortcut Ctrl+B). Add a background color to distinguish headers from data. In Google Sheets, use Format > Number format to set a light gray background; in Excel, use Home > Fill Color. This visual distinction helps participants immediately understand the structure.
2. Set Up Shared Access and Guidelines
Once your template is ready, save it to a shared location where all participants can access it. If using Microsoft 365, save to OneDrive or SharePoint and adjust sharing permissions to allow editing. For Google Sheets, use File > Share and grant "Editor" access to your team members. Send the link along with clear written guidelines about how the retrospective will work.
Include instructions that explain: the time window during which people should add feedback (typically 24-48 hours before the live retrospective meeting), guidelines for keeping feedback specific and actionable (avoid vague statements like "communication could be better"; instead write "engineering updates weren't shared in the product Slack channel during feature development"), and an explanation that all feedback is welcome and shouldn't be taken personally. Consider adding a second worksheet tab labeled "Guidelines" where you place these instructions so they're always visible.
Set expectations about the meeting agenda. Explain that you'll spend the first 15 minutes reading through feedback silently together, the next 20 minutes discussing themes, and the final 15 minutes voting on which action items to commit to. Having this structure established beforehand keeps the meeting focused and moving.
3. Conduct the Asynchronous Input Phase
Open your spreadsheet for input at least 24 hours before your synchronous retrospective meeting. Send a reminder to all team members with the spreadsheet link and encourage them to add their feedback. They should enter items in the "Feedback" column under the appropriate category. Keep the "Owner" column blank for now; you'll fill this during the meeting.
Ask participants to add one idea per row rather than grouping multiple thoughts into a single cell. This structure makes it easier to identify duplicate themes and vote on individual items. If someone thinks of something similar to an entry already in the spreadsheet, they can add a comment or simply leave it and you'll consolidate during the meeting discussion.
Set a reminder for yourself 2 hours before the retrospective meeting to review what has been submitted. Look for obvious duplicates that you can consolidate beforehand (for example, if three people wrote "lack of design specs" in different ways, you might standardize this to a single entry before the meeting). This preparation saves time during the live portion and shows the team you're taking the process seriously.
4. Conduct the Live Retrospective Meeting
Start the meeting with everyone viewing the same spreadsheet, either projected on screen or visible on their individual devices. Go through the "Went Well" section first, reading each item aloud. This positive start builds momentum and reminds people what they accomplished. As you read through the "Went Well" items, ask the team if there are any clarifying questions or related points. Update the "Owner" column with the person who can best articulate why this went well.
Move to the "Needs Improvement" section next. This is where good facilitation matters most. As you read each item, acknowledge it without being defensive. Ask clarifying questions like "Can you give us an example of when this happened?" or "What would have made this better?" Avoid dismissing feedback or explaining why something happened the way it did. Your job is to understand the team's perspective, not defend past decisions.
During discussion, use the "Status" column to track which items are generating action items. Type "Action Item" in this column for any feedback that the team agrees needs concrete follow-up steps. This helps you distinguish between observations (something noted but not requiring action) and actual problems that need solving.
5. Vote on Priority and Assign Action Items
After discussing all feedback, it's time to determine which items warrant action items. Use the "Votes" column to let the team rank priorities. The simplest approach: each person gets 5 votes to distribute across the "Needs Improvement" items they think are most critical. In the spreadsheet, type the vote count directly in column D.
In Excel, you can use a COUNTIF formula to automatically tally votes if you prefer a more sophisticated approach. Create a summary section below your main feedback table and add a formula like =COUNTIF(D:D,">0") to count total items that received votes. This helps identify items that generated zero votes, which you can probably deprioritize. However, for most retrospectives, manual vote counting works fine and keeps things simple.
For items that received the most votes, work with the team to create specific action items. In the "Action Item" column, write what needs to happen (for example, "Create design spec template for future features" or "Schedule weekly product-engineering sync"). Assign an owner in the "Owner" column - this should be whoever is best positioned to drive the change. Set a due date by adding a "Due Date" column (column G) if you don't already have one. Keep action items specific and achievable within the next sprint cycle.
6. Document Action Items in Your PM Tracking System
After the retrospective concludes, transfer action items to your primary project management system. Whether you use Jira, Linear, Azure DevOps, or another tool, create a task or ticket for each action item that received assignment. Link back to the original retrospective spreadsheet in your task description so team members can refer to the original feedback if they need context.
Review your action items with relevant stakeholders within 24 hours of the retrospective. If an action item was assigned to an engineering lead, have a quick conversation to confirm they understand the request and can commit to the timeline. If someone feels an item isn't feasible or contradicts other priorities, better to clarify immediately rather than have it sit incomplete until the next retrospective.
Create a new column in your retrospective spreadsheet called "Task Link" (column H) and paste the URL to the corresponding task in your tracking system. This creates accountability and makes it easy for team members to see progress on action items between retrospectives.
7. Track Action Items Between Retrospectives
Every two weeks (or whatever cadence you use), update the "Status" column with progress notes. Use simple statuses like "Not Started," "In Progress," or "Complete." If an action item is taking longer than expected, add a comment explaining why. This prevents items from disappearing into the void and shows the team you're serious about follow-through.
Consider adding a summary row at the bottom of your spreadsheet that counts how many action items from the previous retrospective were completed. In Excel, use a COUNTIF formula: =COUNTIF(F:F,"Complete"). Track this metric over time. If completion rates are consistently low (below 70%), it signals that either your team is overcommitting during retrospectives or action items aren't being prioritized appropriately. Both are worth discussing at your next retrospective.
8. Archive and Analyze Patterns Across Retrospectives
At the end of each quarter or release cycle, create a new archived version of your retrospective spreadsheet. Keep the original in read-only mode and start a fresh sheet for the next sprint. This historical record is valuable. Over time, you'll notice patterns: certain themes that come up repeatedly, common blockers that never get resolved, or trends in what the team feels is working well.
Create a summary worksheet that lists the top themes from all retrospectives across the quarter. Use a pivot table to analyze this data. In Excel, select your historical data, then go to Insert > PivotTable. Create a pivot table that counts feedback items by category and theme. This gives you a bird's-eye view of whether your team's biggest concerns are being addressed or simply recurring conversation topics that need deeper intervention.
Pro Tips
- Use conditional formatting to highlight cells in the "Status" column. Set rules so "Complete" items show green, "In Progress" shows yellow, and "Not Started" shows red. In Excel, go to Home > Conditional Formatting > New Rule. This gives you instant visual feedback on action item progress.
- If your team is distributed across time zones and can't attend synchronously, extend the asynchronous phase to 48 hours and conduct the live discussion portion as a recorded video. Participants can still watch and add follow-up comments asynchronously, then you formalize decisions in a follow-up message.
- Create a template file with your standard columns and guidelines pre-filled so you don't have to rebuild the structure each sprint. Save this as a blank template that you duplicate for each new retrospective.
- Add a "Theme" column where you manually categorize feedback during preparation. For example, feedback about communication, process delays, and unclear requirements all fall under "Communication & Alignment." This meta-level grouping often reveals deeper patterns than the surface-level feedback.
- Keep retrospectives to 45 minutes maximum. Longer meetings lead to fatigue and lower participation quality. If you have too much feedback to cover, that's actually valuable information suggesting retrospectives should happen more frequently.
When to Upgrade to a Dedicated Tool
Excel works well for most product teams, but there are situations where dedicated retrospective software makes sense. If you're running retrospectives with teams larger than 20 people, specialized tools like tool provide better real-time anonymity and prevent dominant voices from influencing feedback. If you need integration with your sprint planning or project management tools, or if you want to analyze retrospective data across dozens of past sprints without manual effort, consider moving to a dedicated platform.
Teams following more advanced agile-product-management frameworks or those operating in highly regulated industries may also benefit from dedicated tools that provide audit trails and formal documentation. However, for most early-stage product teams and mature teams with strong retrospective discipline, Excel provides sufficient functionality at zero additional cost. Check our PM tools directory to explore alternatives when the time comes.