5 exercises on retrospective phrases. Choose the most natural and professional option.
0 / 5 completed
1 / 5
You are opening the 'what went well' segment of a retrospective. Which phrase invites honest sharing without putting anyone on the spot?
Option C is best because it does two things at once: it models the behaviour you want (sharing a specific observation) and ends with an open invitation for others to contribute. Simply asking 'What went well?' (A) can leave the room silent because no one wants to go first. 'Tell me what went well' (B) sounds like an interrogation. 'Let's start the retro now' (D) is not even an invitation — it is a procedural announcement. Experienced facilitators seed the discussion by volunteering a concrete example, lowering the social risk for everyone else.
2 / 5
You want to suggest a process improvement diplomatically during the retro. Which phrasing is most effective?
Option A is the professional standard. It frames the idea as something you would 'love to see us try' — collaborative, forward-looking, and specific (30 minutes, before merging to main). 'We should have reviews before merging' (B) is vague and preachy. 'The reviews were bad this sprint' (C) is backward-looking and critical without a solution. 'People need to review code better' (D) implies blame without naming a specific improvement. In retros, the best suggestions are concrete, future-focused, and framed as experiments rather than mandates.
3 / 5
The team has identified a problem and you want to turn it into a concrete action item. Which phrase works best?
Option D is correct because it follows the golden rule of action items: named owner, clear deliverable, time-bound deadline. 'We should fix this' (A) has no owner and no deadline — it will be forgotten. 'Somebody needs to do something about this' (B) is even vaguer — 'somebody' almost always means nobody. 'Let's discuss this more next time' (C) defers without committing. In agile retrospectives, every action item must answer three questions: who, what, and when. Option D answers all three.
4 / 5
During the retro, someone points out a problem with code you wrote. How do you respond most professionally?
Option B is the most professional response. It acknowledges the feedback ('fair point'), shows self-awareness ('I underestimated the complexity'), and immediately redirects to a constructive question ('What would have helped?'). This models psychological safety for the rest of the team. 'That's not fair — I did my best' (A) is defensive and shuts down conversation. 'I don't agree' (C) without elaboration sounds combative. 'Thanks for the feedback' (D) is polite but passive — it does not contribute to improving the team's process.
5 / 5
You are closing the retro and want to move from discussion to action. Which phrase closes the meeting most productively?
Option A is the professional standard for closing a retro. It confirms you will capture action items, ensures every item has an owner (preventing diffusion of responsibility), and promises a written summary. 'OK, retro is done' (B) closes without consolidating anything. 'That's enough for today' (C) sounds dismissive. 'We're finished, goodbye' (D) is abrupt. A strong retro close always includes a read-back of action items, owner assignment, and a commitment to a follow-up record. Without these, retrospectives rarely generate lasting change.