Template
Team retrospective
The classic format (went well, didn't work, try next) plus a mood thermometer. Anonymous so the truth comes out, and the AI clusters answers by theme.
Who it's for: Product and engineering teams, or any group that closes cycles and wants the next one to be better.
No card · Opens already built in your editor
-
How was this sprint? (1 = awful, 10 = textbook) *
-
What went well? *
-
What didn't work? *
-
What should we try next sprint?
When to use it
- You're closing a sprint or project and want the retro written BEFORE the meeting, so the meeting is for deciding, not remembering.
- The team is remote or hybrid and the live retro is always dominated by the same two voices.
- You sense friction nobody verbalizes: anonymous writing surfaces what the table round swallows.
What's inside and why
- How was this sprint? (1–10)
- The numeric thermometer turns feeling into a time series: a 6 after three 8s is the early warning no open question gives you.
- What went well?
- Starting positive isn't politeness: it identifies practices to protect before the problem list monopolizes the conversation.
- What didn't work?
- Open and anonymous: the real blockers show up here. The AI clusters answers and turns 12 paragraphs into 4 themes.
- What should we try next sprint?
- Asking the person who flags the problem for the proposal turns complaint into experiment — and it arrives at the meeting already formulated.
Tips to get the most out of it
- Send it 24h before the retro meeting and project the AI-clustered themes: the meeting starts at minute 0 with the substance.
- Keep the same 4 questions sprint after sprint: the thermometer series (7, 8, 6…) warns earlier than any other signal.
- Pick ONE “try next” proposal per sprint. A retro that produces five actions produces zero.
Frequently asked questions
Is it truly anonymous?
Yes: it starts with «Anonymous responses» on: no name, no email, and no time or IP stored with each answer. In very small teams, avoid quoting sentences verbatim in the meeting: style gives more away than a name.
Does it replace the retrospective meeting?
It upgrades it: collection becomes async and written (more honest, more complete), and the meeting keeps what genuinely needs conversation — deciding what to try next sprint.
How often should we run it?
At the close of every sprint or cycle (every 1–4 weeks). Consistency beats frequency: it's the thermometer-and-themes series that reveals trends.