HeyRetro use cases Updated 7 min read
Your first retrospectivea simple guide for the team
Give the team a clear purpose, quiet time to think, and one small action they can see through before the next meeting.
Your first retrospective should prove that team reflection can produce a small, visible improvement people can point to when the group meets again. Keep the format simple and explain how people can take part. One action is enough for the first meeting.
Before the meeting
- Choose a 40–45 minute timebox.
- Define the sprint, project, or period being reviewed.
- Open the Classic Sprint template.
- Explain that the meeting improves the working system. Performance reviews happen elsewhere.
- Bring a short set of useful facts for context.
A beginner-friendly agenda
- Purpose and ground rules, 5 minutes.
- Silent card writing, 7 minutes.
- Read, clarify, and group, 8 minutes.
- Vote across themes, 5 minutes.
- Discuss the leading pattern, 10 minutes.
- Assign one action, 5 minutes.
Prompts that work
- What helped the team make progress?
- Where did work become harder than it needed to be?
- Who helped, and which behavior should be repeated?
- What is one condition the team can change before the next review?
How to build trust in the practice
Let everyone write before senior voices enter the conversation. People can decide how much context to share about a feeling. End with one small action the team controls, then open the next retrospective by checking what happened. The full meeting guide adds timing and ground rules.