Retrospectives are one of the best tools in team practice — and one of the most commonly wasted. A retro that produces a list of observations and no committed actions is 45 minutes of venting with a whiteboard. The format is simple; the discipline of making it useful is not. Here is how to run retros in 2026 that teams actually look forward to, because they see them change things.
What changed in 2026
- Async retros are now standard for many distributed teams. Tools like Parabol, EasyRetro, and Miro let teams submit items before the meeting, reducing the blank-stare problem and surfacing quieter voices.
- AI retro summarizers can cluster similar items and highlight themes across multiple sprints — useful for trend analysis, not for replacing the conversation.
- Psychological safety is a measurable metric at more companies now. Teams that track eNPS and safety scores know whether retros are surfacing real issues or just producing safe, positive feedback.
- Shorter sprints (one and two-week cycles) mean retros need to be shorter and sharper — longer feedback loops allow longer retros; weekly cycles force 30-minute retros.
The standard format (60 minutes)
| Phase |
Time |
What happens |
| Check-in |
5 min |
Quick one-word or one-sentence pulse |
| Review last retro's actions |
5 min |
What got done? What did not? Why? |
| What went well |
10 min |
Sticky notes or async pre-fill, group and dot-vote |
| What did not go well |
15 min |
Same process; allow anonymous submission |
| What to change |
15 min |
Identify top 1–3 themes, discuss root causes |
| Action items |
10 min |
Define specific actions, assign owners, set due dates |
Step-by-step facilitation
Before the meeting
Send the retro prompt 24 hours ahead. Ask people to add items in the shared board asynchronously. This warms the room, removes "I can't think of anything on the spot" answers, and gives introverts equal voice.
Opening
Start with the check-in word or phrase. It humanizes the room and signals that this is not a status meeting. Then spend 5 minutes on last retro's actions — this is the accountability beat that makes the whole practice credible.
Gathering items
Set a 3-minute silent brainstorm for each column. Everyone writes simultaneously. No discussion yet.
Dot voting
Give each person 3–5 votes to place on items they care most about. Vote before discussion to prevent anchoring on whoever speaks first.
Root cause on top items
For the 2–3 items with most votes: ask "why did this happen?" not "what happened?" One level deeper produces actionable insights.
Action items
Before the meeting ends, every agreed change must have:
- A specific, concrete action (not "improve communication" — "add a daily async update in #team-updates")
- An owner (one person, not "the team")
- A due date (by when, not "soon")
Write them publicly. Check them at the start of the next retro.
Retrospective formats beyond the basic
| Format |
Best for |
| Start / Stop / Continue |
Simple, fast, direct |
| 4Ls (Liked, Learned, Lacked, Longed for) |
Learning-heavy sprints |
| Sailboat |
Visualizing goals vs. obstacles |
| Mad / Sad / Glad |
Emotionally charged periods |
| DAKI (Drop / Add / Keep / Improve) |
Process-heavy teams |
Vary the format occasionally to prevent retro fatigue.
Common mistakes
No action items. A retro without committed next actions is just a conversation. Every retro must end with 1–3 specific actions.
Too many action items. Committing to 8 actions means 7 won't happen. Limit to 3 maximum; completion beats aspiration.
Skipping the "review last retro" step. This is how trust and credibility build. If actions never get reviewed, people stop believing retros matter.
Dominant voices running the room. Use silent parallel brainstorm + dot vote to equalize. The loudest person's opinion is not automatically the most important.
Using the retro to assign blame. Focus on process and systems, not individuals. "The deploy process had no rollback step" is useful. "Dev didn't test properly" is not.
What to skip
- Retros longer than 60 minutes. Longer retros dilute focus. If you have more than 60 minutes of material, you waited too long between retros.
- Facilitation without psychological safety measures. If people don't feel safe, you will get performance, not honesty.
- Public naming of individuals in the "what went wrong" section. Keep it to process observations.
FAQ
How often should we run retros?
Match retro cadence to sprint length. Two-week sprint: one retro per sprint. Longer cycles: at least monthly. Never go more than six weeks without one.
What if the team always says everything is fine?
Introduce anonymous input. "Everything is fine" is almost always a safety signal, not a truthful assessment.
What if the same items keep appearing every retro?
That means the action items from previous retros didn't address root causes. Run a 5-whys session on the recurring item.
Should the manager attend?
If managers attend, psychological safety often drops. Many teams run more honest retros with just the working team. Manager can review the summary afterward.
Where to go next
See How to set OKRs in 2026, How to run a standup in 2026, and How to delegate tasks in 2026.