16 retrospective questions for teams and personal reviews

Choose retrospective questions for a particular period and difficulty. You do not need to complete a long list as though it were a survey. Select a few prompts, reconstruct what happened and finish with a decision you can examine in practice. Below are 16 editorial questions for a team discussion or a personal work review.

Choose a focus before the conversation

Define the boundary: a project stage, a series of learning sessions or a working week. State what the discussion should help you do: understand a recurring delay, retain a useful practice or assess a change already tried. “Discuss everything” leaves the scope too broad.

The Atlassian retrospective guide covers positive experiences, difficulties, lessons and changes. Our collection turns those directions into more specific observations. These are prompts to select from, not a mandatory meeting standard.

Prepare relevant records such as agreements, deadlines and the results of attempts. Personal feelings can be included without presenting them as the whole team’s assessment. For the meeting sequence, read the guide to running a team retrospective.

Questions about what to retain

• In which specific episode did the work proceed more easily than usual?
• What actions or conditions were available during that episode?
• Which of those can we repeat, and which depended on circumstances?
• Who else benefited from the approach, and how did we learn that?

Suppose a document was reviewed quickly. Check whether it was shorter, had a different reviewer or used requirements agreed in advance. Do not automatically conclude that a new document format resolved every source of delay.

Keep the same specificity in a personal review. “On Wednesday I prepared the session without searching for materials” gives you more to examine than “I was organised this week”. Record conditions worth repeating, as well as acknowledging the result.

Questions about difficulties and missing information

• At which step did expectations and the actual sequence diverge?
• What information was available to the person when they made the decision?
• What information are we still missing to understand the event?
• Which possible explanation should we investigate before selecting a solution?

If a task was delayed, reconstruct the handover, access to material and agreed outcome. “People need to be more responsible” does not identify what was missing. Where several explanations remain, a fishbone diagram can help organise them.

Do not require someone to disclose personal circumstances to make the discussion feel complete. A team can recognise an availability constraint and reconsider a working agreement without examining its private causes in front of the group.

Questions about decisions and collaboration

• Was it clear who would make the decision and who would provide information?
• Where did participants understand the expected outcome differently?
• Which feedback arrived in time to influence an action?
• What did we change during the work, and why did we choose that adjustment?

Compare perspectives without immediately forcing them into one account. One person may have considered a task handed over while another was waiting for confirmation. The useful next step is an agreement about the handover point, rather than a vote on who was right.

For a personal retrospective, adapt the questions: which decision was yours to make, what help needed to be requested and what did you learn too late? Do not assume responsibility for controlling other people’s actions.

Questions that lead to an action

• What one change are we prepared to try in the next cycle?
• Who will organise the trial, and what support will they need?
• What will we observe to understand how the change worked?
• When will we return to the result and decide what to do next?

In an illustrative example, replace “Improve communication” with an agreement to confirm a received task and its expected outcome in one place. After the next handover, check whether that happened and which questions remained.

Keep the answers needed for the selected action. Other topics can remain on a separate list rather than becoming commitments without owners. For a focused examination of one episode, use the guide to reviewing an attempt and its outcome. Questions earn their place by helping clarify the next piece of work.