> For the complete documentation index, see [llms.txt](https://guides.tability.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.tability.io/docs/become-a-tability-power-user/ai-mode-how-tos/prepare-team-retrospective.md).

# Prepare a team retrospective

Review a month of check-ins and results to identify lessons and practical changes for the next period.

Turn the team's recent work into a useful discussion about what to keep and what to change. AI Mode can review the recorded results and check-ins, then draft a retrospective for the team to refine.

**For:** Managers · **Where:** AI Mode inside Tability

## Watch the walkthrough

{% embed url="<https://318707989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMULqjSmZyGczPy2I6FGH%2Fuploads%2Fgit-blob-e3280549e9c611754bcc0111440610eae58083d3%2Ftability-ai-mode-retro.mp4?alt=media>" %}
Review the month’s results and patterns, then identify changes for the next month. 30-second demo, no audio; fictional workspace data.
{% endembed %}

## 1. Set the period and team

Open **AI Mode** and give it the team or plan links and the month to review.

```
Prepare a team retrospective for [team or plan links] covering [month and year]. Review the key results, that month's check-ins, and related initiatives.

Cover where the month landed, what went well, what did not, recurring patterns, and what we could change next month. Link the evidence and distinguish recorded facts from possible explanations. Flag missing check-ins. Draft the retrospective in chat and create a concise visual summary in the artifact panel. Do not save a plan retrospective or change records yet.
```

Add important context from the team that is not in the workspace. Goal records show only part of the story, so use the draft to open a discussion rather than to settle the causes in advance.

## 2. Discuss the patterns

Check that each lesson follows from the evidence. Ask the team whether the explanation fits their experience, especially where delays involve dependencies or changes in scope.

```
Turn the strongest lessons into three proposed changes. For each, explain the evidence, the behaviour we would change, an owner to agree, and how we would know it helped. Separate ideas from agreed commitments.
```

Keep the final list short enough to act on. Avoid carrying every unfinished task forward without checking whether it still matters.

## 3. Capture the agreed follow-up

Return with the team's decisions and ask for the final retrospective. If you want it saved to a plan, name the plan and review the proposed text before approving the save. See [Retrospectives](https://guides.tability.io/docs/become-a-tability-power-user/features/reporting/retrospectives.md).

For new work, ask AI Mode to preview [initiatives under the relevant key results](https://guides.tability.io/docs/become-a-tability-power-user/ai-mode-how-tos/turn-goal-into-action-plan.md). You can download the visual summary from the artifact panel for your meeting notes.

**Done when:** the team agrees on the lessons and a small number of concrete changes for the next period.

Explore the other [AI Mode how-tos](https://guides.tability.io/docs/become-a-tability-power-user/ai-mode-how-tos.md).
