Retrospective meeting template

TL;DR: Most retrospective templates are fill-in documents where action items quietly die between sprints. This guide gives you a three-column structure (what went well, what to improve, action items) with owner and due date fields, plus facilitation notes for each column. The problem isn't the conversation. It's what happens after it. Pairing a structured template with an AI notepad like Granola means the facilitator stays focused on the team while every commitment gets captured, assigned, and surfaced before the next session.

Most teams run retrospectives because their agile process requires them to, but the same problems surface sprint after sprint because action items disappear into Slack threads and never get tracked. Retrospective action items routinely get lost between sprints, which is worse than skipping the conversation, because it teaches the team that retrospectives don't change anything.

The fix isn't a better discussion. It's a better system for moving from discussion to documented, tracked commitments. This guide gives you a fill-in retrospective template with owner tracking, facilitation strategies for each column, and a workflow for closing the loop before your next sprint.

What is a retrospective meeting?

Purpose of retro meetings

The goal is to improve the system, not assign blame. That distinction matters because teams that treat retrospectives as debriefs rather than accountability sessions get more honest input. Wins get recognized, friction points get surfaced, and the team leaves with a short list of concrete improvements to act on, not a long list of grievances to forget.

Who should attend

The core attendees are the product team, engineering team, designers, and the facilitator (the Scrum Master or team lead). External stakeholders are typically not included in day-to-day sprint retrospectives, though engaging broader leadership after major initiatives can be worth considering. Psychological safety, the shared belief that the team is safe for honest discussion, depends on participants feeling supported rather than evaluated, so keep the default group tight and expand it deliberately.

When to run retrospectives

The most common cadence is at the end of every sprint, typically every two weeks. Echometer's analysis of 30,000 retrospectives found the ideal duration is 30 to 60 minutes, with shorter sessions rating more satisfying, and recommends a 7 to 14 day cadence. You can also run them at the end of a major project phase or after a critical incident, adjusting the duration accordingly.

Retrospective template structure

The classic three-column structure is a strong default because it's simple enough to fill in under time pressure and specific enough to produce real action items. That said, using the identical format every sprint eventually causes participants to predict what will be said before anyone speaks, which reduces honest input. Use the three-column template as your foundation and rotate alternatives periodically to maintain engagement.

Before choosing your format, consider where your team does its best thinking.

For most teams, a document-based format tends to help with follow-through because action items stay searchable and live in the same tools used for sprint planning.

The fill-in retrospective template

Copy this template into Notion, Confluence, or your preferred doc tool before each session.

Retrospective: Sprint/Iteration [number] | Date: [date] | Facilitator: [name]

Attendees: [list names]

Sprint goal: [one line]

Review of last retro's action items:

What went well

What to improve

Action items

The action items table is the most important section. Every row must have exactly one owner, a specific date, and a definition of done that makes it clear whether the item was completed.

Advanced retrospective frameworks

Here are six worth keeping in rotation:

1. Sailboat: Maps an island (goal), wind (what's propelling you), anchors (obstacles), and rocks (risks ahead). Good for project-phase retrospectives where strategic context matters.
2. 4Ls (Liked, Learned, Lacked, Longed For): Explicitly surfaces learnings, making it particularly effective for building a culture of continuous improvement.
3. Mad Sad Glad: Places emphasis on individual team member emotions, useful when morale has been a recurring theme.
4. Battery: Each team member rates their current energy level from empty to full. Good after high-intensity sprints or product launches to surface burnout risks before they compound.
5. Starfish: Five zones: Start (new practices to begin), More Of (existing strengths to amplify), Keep Doing (positive aspects to maintain), Less Of (areas to scale back), and Stop (activities to discontinue). Gives teams a more granular way to calibrate behavior than binary start/stop models.
6. Start-Stop-Continue: Direct and fast, a simpler three-zone alternative. These alternative formats serve a secondary purpose beyond preventing meeting fatigue. Templates like Mad Sad Glad or the Battery give team members structured ways to express emotional states or capacity concerns that don't fit cleanly into a "what to improve" observation. When psychological safety is fragile or team health is declining, these frameworks can surface issues that the standard three-column format misses.

How to facilitate each column

Facilitation is the skill that separates a retrospective that produces real change from one that produces a document nobody reads. Starting every session by reminding the group of Norm Kerth's Retrospective Prime Directive sets the right frame: regardless of what the team discovers, everyone did the best job they could, given their knowledge, skills, resources, and the situation at hand. That framing prevents the session from becoming a blame exercise and creates the psychological safety that honest input requires.

Facilitating 'what went well'

Start with a silent writing period of five to ten minutes before anyone shares. This prevents dominant voices from anchoring the group and ensures quieter team members contribute. When reflections aren't visible to others during the input phase, participants share more honestly, because there's no opportunity to anchor on someone else's framing. Celebrate small wins alongside major milestones. Recognizing process improvements, not just shipped features, reinforces the behaviors you want to repeat.

Facilitating 'what to improve'

Use the same silent writing approach, then move to affinity mapping: group similar observations together before discussing them. Dot voting is an efficient way to prioritize. Each person receives a set number of votes (typically three to five) and marks the observations they feel are most pressing. The team then discusses the highest-scoring themes first. This approach handles both quiet teams and dominant voices by anchoring discussion on aggregated input rather than whoever speaks first.

Guide the team toward describing systemic friction rather than individual behavior. "Our deployment process has too many manual steps" generates an actionable improvement. "Alex keeps breaking the build" does not.

Turning discussion into actions

This is the moment most retrospectives stall. For a standard 60-minute retrospective, a practical time allocation looks like this:

The transition from "what to improve" to "action items" requires the facilitator to push the team from describing problems to committing to solutions. A useful prompt: "What is the one specific thing we could do before the next sprint that would reduce this friction?" Limit the team to three high-priority action items. More than that and focus dilutes.

Assigning owners effectively

Ask for volunteers before assigning. When a team member chooses an action item rather than being handed one, follow-through rates improve. The single ownership rule is non-negotiable: if two people own a task, neither owns it. One lead, with others listed as contributors or reviewers if needed.

How to capture retrospective discussions

The facilitator's central challenge is being present in two places at once: guiding the conversation and documenting what's being said. Traditional note-taking forces a real trade-off. The facilitator either keeps up with typing and misses the room, or stays engaged and loses detail. This is where the documentation system matters as much as the template itself.

Transcribing the conversation

We designed Granola to capture device audio and transcribe in real time, working across Zoom, Google Meet, Teams, Slack Huddles, and any other platform your team uses. You jot a few key phrases during the session, and Granola uses the live transcript to fill in the full context once the meeting ends. Your notes stay in black. Granola's additions appear in gray, so you always know what you wrote versus what the AI enhanced.

Audio is deleted immediately after transcription. We achieved our SOC 2 Type 2 certification in July 2025 and contractually prohibit third-party AI providers from training on your data. You can also enable our transparency features, including an automatic in-chat notification that Granola is transcribing, so every participant is informed from the start.

Documenting key decisions

Our human-in-the-loop approach keeps the facilitator in control of what gets captured. Write "Deployment pipeline is the bottleneck" during the meeting, and Granola finds every reference to that theme in the transcript and fills in the supporting detail. Leave the notepad blank and get a generic summary.

The quality of the output reflects the quality of the input, which keeps the facilitator's judgment at the center of the documentation rather than replaced by it.

Synthesizing themes across sessions

Some teams use Granola Chat to synthesize themes across multiple sessions. Asking "What friction points appeared most often in Q1 retros?" surfaces patterns that can feed into roadmap planning or sprint prioritization. Our Notion integration (Business plans) lets you send these insights to your Notion database with one click, and the Zapier connection can route action items into tools like Asana, so retrospective outputs flow into existing workflows rather than sitting in archived documents.

Preserving context for future retros

A searchable archive of past retrospectives addresses what teams sometimes call "retrospective amnesia," where teams forget why decisions were made and recreate the same conversations sprint after sprint. Create a shared "Team Retrospectives" folder in Granola and every session becomes queryable. Ask "What are our recurring bottlenecks over the last three months?" and Granola returns source-linked citations from specific sessions rather than requiring you to manually review ten documents.

Tracking action items between retrospectives

Carrying actions to the next retro

Start every retrospective by reviewing the action items from the previous session before generating new ones. Celebrate completed items, even small ones. Reassess anything in progress and be honest about what to keep, modify, or drop.

Following up on commitments

Keep action items visible between sprints. Pin them in the team's Slack channel, add them to the sprint board, or sync them to Jira. Our Notion and Slack integrations on Business plans automate distribution so the team sees action items without the facilitator manually forwarding documents after every session.

Closing the loop on improvements

When the next retrospective opens and the team reviews previous action items, the goal isn't just checking boxes. It's measuring whether the change worked. If an implemented change didn't reduce the friction it was meant to address, bring it back into the "what to improve" column and approach it differently. This closing-the-loop discipline turns retrospectives from venting sessions into continuous improvement systems.

Common retrospective mistakes to avoid

Skipping action item follow-up

Failing to review previous action items at the start of the next retrospective destroys team trust faster than any bad sprint. When the team sees that commitments made in the last session were never tracked or discussed, they stop believing retrospectives change anything. That belief, once formed, is hard to reverse.

Letting discussions run too long

Timebox each phase. When a point only involves two or three team members, park it. Note it as an offline discussion item and move on. The facilitator's job is to serve the whole team's time, not to resolve every issue in the room. Strict time allocation is one of the most consistent differentiators between effective and ineffective retrospectives, which is why the time breakdown in the facilitation section above matters as much as the template itself.

Losing psychological safety

Blame-shifting, sarcastic framing, or allowing individual criticism to replace systemic analysis will kill participation quickly. The prime directive exists for this reason. Retrospective notes used punitively in performance conversations will cause team members to stop giving honest feedback within a sprint or two. Keep retrospective documentation within the team and use it to drive process improvement, not evaluation.

We built Granola to let you facilitate retrospectives without choosing between being present and capturing detail. Download the Mac or Windows app, connect your calendar, and run your next retrospective to see how we capture the conversation and carry your action items forward automatically.

FAQs

How do I make retros actionable?

Never close the meeting with an action item that lacks a single named owner and a specific due date. Limit the team to three high-priority items per sprint. If an item is too vague to assign a definition of done, it isn't ready to be an action item yet.

Should we use the same template every time?

Use the standard three-column template as your default, but rotate in an alternative framework periodically. Repetition reduces engagement, and lower engagement produces less honest input. Variety keeps the format feeling like a genuine reflection rather than a box to check.

How does Granola handle privacy during sensitive retrospectives?

Audio is deleted immediately after transcription. We achieved SOC 2 Type 2 certification in July 2025 and are GDPR compliant. You can enable an automatic in-meeting notification so all participants know transcription is active.

Key terms

Retrospective: A meeting held at the end of a sprint or project phase where the team reflects on what went well, what to improve, and what specific actions to take before the next cycle.

Action item: A discrete, documented task arising from a meeting that has a single named owner, a specific due date, and a measurable definition of done.

Psychological safety: A shared team belief that honest input during retrospectives won't be used against individuals, enabling more candid participation and more useful feedback.

AI notepad: A digital notepad where the facilitator jots rough notes during a meeting, which are then enhanced by AI using real-time transcript context. The facilitator's notes guide what the AI surfaces from the transcript.