Free meeting tools
Free Team Retrospective Template
Turn recent experience into a change the team can try. Gather observations, explore a useful theme and leave with an owner and a review date.
No signup. Edit in your browser. Download Word .docx, text or Markdown.
Edit this templateA clear agenda. A useful record.
2. Add meeting details
All fields are optional. Apply your details when ready. Your latest edited draft stays available to restore.
Your notes stay in this tab.
Entries and drafts are kept in browser memory. Reloading or leaving this page clears them. Download a copy to keep your work.
3. Edit, copy or download
Ready to make your ownReplace the prompts in square brackets. Add notes during the meeting, then confirm decisions, owners and deadlines.
Word .docx opens in Microsoft Word and can be uploaded to Google Docs. .txt is plain text; .md adds Markdown headings. No document is uploaded automatically.
When to use this template
Use this outline after a sprint, project or agreed period of work. Give people time to describe their experience before choosing a solution. Focus on a change within the team's control and revisit the previous experiment so actions do not disappear after the meeting.
Make it useful for your meeting
1. Set a clear period to review
Name the project or dates and check what happened to the previous improvement. Agree to discuss the work respectfully. Explain how notes will be used before participants contribute.
2. Gather observations before conclusions
Ask what helped, what made work harder and what surprised people. Invite concrete examples and time to think. Separate an observed event from a possible explanation for it.
3. Choose a theme the team can affect
Look for a recurring issue or a useful opportunity. Ask which contributing factors are supported by the observations. Discuss options and avoid assigning a cause to a person without checking the context.
4. Make the improvement testable
Choose one specific change, an owner and a review date. Name what the team will observe to decide whether it helped. Keep the action visible alongside the next period's work.
A filled-in example
Fictional team example. Use it to see the level of detail, then adapt the editor above for your meeting.
Guide project retrospective Attendees: Alex, Sam and Jordan Period reviewed: The account setup guide update. Helped: Sam shared the outline before drafting screenshots. Hindered: Review ownership was unclear until Thursday. Observation: Two drafts waited for a reviewer to be assigned. Theme selected: Confirming review responsibility earlier. Experiment: Name the reviewer when each writing task is accepted. Owner: Alex will add the reviewer to the next task brief. Review date: The next project check-in. Evidence to discuss: Whether each draft had a reviewer before it was ready for comments.
Common questions
Which retrospective format does this use?
It uses observations about what helped, hindered and surprised the team, followed by a focused improvement experiment. You can replace the prompts with a format your team prefers.
How many improvement actions should we choose?
The outline starts with one manageable change. Choose a scope the team can own and review. A long list of unowned suggestions is difficult to follow through.
Are retrospective comments anonymous?
The editor is a local document, not an anonymous collection service. Notes are visible to whoever can see the screen or receives the file. Agree how comments will be recorded and shared before collecting them.
Your document stays in this tab. Copy or download it before leaving. The editor does not record a call, send your notes or save them to an account.