Retrospectives are one of the most valuable rituals an agile team can run — and one of the most commonly wasted. The format isn't the problem. Teams know how to do Start/Stop/Continue. The failure point is almost always at the end: a long list of good ideas, no clear winner, and an action item assigned to everyone that nobody owns. This guide covers how to pick the right format, facilitate the session effectively, and use structured voting on action items to turn retrospective output into actual change.
What is a retrospective?
A retrospective (or "retro") is a structured team meeting held at the end of a project phase or sprint, focused on process improvement rather than output. The team reflects on how they worked together, what friction slowed them down, what practices helped, and what they want to try differently. Retros are different from project post-mortems (which are typically held once at the end of a project) in that they're recurring — every 1–2 weeks in most agile environments. The frequent cadence is the point: small, regular adjustments compound over time into significantly better team performance. A well-run retrospective surfaces problems early, builds psychological safety (because raising issues is the expected norm), and creates an ongoing feedback loop between how the team works and how they'd like to work.
Choosing a retrospective format
Start/Stop/Continue — best for beginners
This is the simplest and most commonly used retrospective format. The team answers three questions: What should we start doing that we currently aren't? What should we stop doing because it's not helping? What's working well that we should continue? Each person writes responses individually (typically on sticky notes or a digital equivalent), then shares with the group. Ideas are grouped into themes, discussed briefly, and then the team selects which to prioritize. The simplicity makes it easy to facilitate without special training and quick to run in under 60 minutes.
Run the brainstorm phase silently and independently before sharing. When people write their ideas before hearing others, you get more diverse and honest responses.
4Ls (Liked, Learned, Lacked, Longed For) — best for depth
The 4Ls format adds nuance beyond positive/negative. Liked: what worked well and should be preserved. Learned: new knowledge or skills gained during the sprint. Lacked: what the team was missing — resources, clarity, skills, or processes. Longed For: what team members wish had been different. The Learned and Longed For categories often surface issues that Start/Stop/Continue misses — particularly knowledge gaps and systemic resource constraints. Best used for teams that have established the basic retrospective habit and want deeper diagnostic value.
Mad/Sad/Glad — best for team health
This format centers emotional experience. Mad: what frustrated team members or felt wrong. Sad: what disappointed or felt like a missed opportunity. Glad: what made team members proud or happy. The emotional framing is particularly useful when team morale is low or when significant conflict or stress occurred during a sprint. It explicitly validates emotional responses to work — which makes it easier for team members to surface interpersonal or cultural issues that more task-focused formats don't reach. Requires higher psychological safety to use effectively.
Running the vote on action items
Why voting is necessary — and why in-room voting fails
After the discussion phase, most retrospectives have generated 10–20 ideas. The team can realistically act on 1–2 in the next sprint. Without a structured selection process, this becomes either a negotiation between the loudest voices or a facilitator judgment call. Both produce low team buy-in. Voting distributes the selection across all voices equally and makes the priority transparent. The challenge with in-room voting is that it's subject to anchoring (people vote after seeing what others chose) and social pressure (people vote with the manager or the most senior person). Anonymous voting solves both problems.
Set up an async vote after the session
After the retrospective meeting ends, compile the list of prioritized action item candidates into a Chooseday decision. Use dot voting to give each team member a fixed number of points to distribute across the options (this works better than single-choice voting for prioritization). Share the link in your team's Slack channel or email it to all attendees. Set a deadline of 24–48 hours. This gives team members time to reflect without the social pressure of voting in the room, and ensures that anyone who left early or was partially distracted still gets a vote.
Dot voting is ideal for retrospective prioritization because it surfaces not just the top choice but the relative enthusiasm for all options — which tells you both what to do next and what to revisit later.
Announce the result and assign ownership
When the vote closes, share the results in the team channel: "The team voted — our next retro action item is X (received 18 of 35 points). Owner: [Name]. Target: complete by [date]." Assign a single owner to each action item — not the team collectively. Shared ownership reliably produces no ownership. Document the result in your project management tool with a due date. At the next retrospective, the first agenda item is reviewing whether the previous action item was completed.
Turning votes into decisions that actually stick
The retrospective is only as valuable as the change it produces. Most teams that run retros regularly have some version of the same problem: the same issues come up sprint after sprint without resolution. This happens because action items are assigned to the team collectively, have no deadline, and get displaced by delivery pressure. Three practices prevent this. First, limit action items to one or two per sprint — trying to improve everything at once improves nothing. Second, assign a single named owner with a specific deadline, not a team responsibility with a vague timeline. Third, review the previous action item at the start of the next retro before generating new ones. Tools like Chooseday support this by making the voted result permanent and shareable — you have a record of what the team decided and when. That record creates accountability in a way that a whiteboard photo or meeting notes never quite does.
Frequently asked questions
A sprint retrospective is a meeting held at the end of a sprint (typically every 1–2 weeks in agile teams) where the team reflects on what went well, what didn't, and what they want to change in the next sprint. The goal is continuous improvement — surfacing process issues early and making small, concrete adjustments before they compound. Retrospectives are most valuable when they produce specific, accountable action items rather than general observations.
After a retrospective session generates a list of potential improvements, the team votes to prioritize which ones to actually work on. Common approaches include dot voting (each person gets a set number of points to distribute across items), thumbs up/down approval voting, or ranked choice for more nuanced prioritization. Running this vote asynchronously after the meeting — using a tool like Chooseday — gives everyone time to reflect and avoids the social pressure that shapes in-room voting.
For a two-week sprint, a retrospective typically runs 60–90 minutes. Shorter sprints may warrant 45-minute retros; longer project phases may need up to 2 hours. A common mistake is letting retros run long in the discussion phase and then rushing the action item selection. Separate the generation phase (broad, inclusive) from the prioritization phase (structured, time-boxed), and consider running the final prioritization vote asynchronously after the meeting to give it the time it deserves.
Start/Stop/Continue is the best format for first-time retrospectives. It's easy to understand, covers the key dimensions of team reflection, and generates actionable output quickly. It asks three questions: What should we start doing that we aren't? What should we stop doing? What's working that we should continue? The simplicity makes facilitation easy and helps the team build the habit of regular retrospection before introducing more complex formats like 4Ls or Mad/Sad/Glad.