HeyRetro use cases Updated 7 min read
Your first retrospectivea simple guide for the team
Use a simple format, explain the purpose, protect equal contribution, and leave the first session with one credible action.
Your first retrospective should prove that team reflection can produce a small, visible improvement. Keep the format simple, make participation boundaries clear, and resist turning every note into an action.
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 and is not a performance review.
- Bring no more than a few 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 speak. Do not force authors to defend feelings. End with one small, controllable action and start the next retrospective by reviewing whether it happened. Read the full meeting guide when you are ready to deepen the facilitation.