Run A Team Retrospective

Visual Space manual, Live Apps, Run A Team Retrospective

This is the read-only HTML version. For the full Visual Space experience, open the app.

Visual Space manual, Live Apps, Run A Team Retrospective

Visual Space manual, Live Apps, Run A Team Retrospective

This walkthrough helps a facilitator guide a team from an empty retrospective board to a small set of clear follow-ups. Participants will contribute attributable feedback, refine their own cards, acknowledge useful points, discuss themes, and confirm that the shared record is ready to revisit. For the feature’s broader purpose and boundaries, start with [Retrospectives](../retrospectives.md).

Guide a team from individual observations to a few agreed changes. This walkthrough uses the three retrospective columns, author-owned cards, reactions, and linked discussion to leave a record the group can revisit after the session.

Frame the Conversation

Choose what the group is reviewing: a sprint, release, incident, event, or project phase. A prompt such as What helped or slowed this release, and what should we change next? gives everyone the same starting point.

•
Prepare the board - Follow Create and Open a Retrospective if it does not exist yet. Use a location every participant can access.
•
Choose how to meet - Open the board individually in Retros, or put it on an activity meeting stage through Live Apps → Retrospectives. Standalone editing requires Coordinator; the meeting workspace supports participants under the board's area access and card-author rules.
•
Provide background - Point people to the linked Article when there is an agenda or evidence to read. Keep the central question short enough to repeat aloud.
•
Set a useful outcome - Aim for a small set of specific actions the team understands, rather than a large board nobody will revisit.

Gather Observations Before Discussion

Explain the fixed columns: Went Well for strengths, To Improve for friction, and Action Items for next steps. Give people a quiet reflection period so the first speaker does not determine every topic.

•
Add one clear point per card - Select Add Card in the relevant column and type directly. Pairing unblocked two difficult reviews is more useful than Teamwork was good.
•
Separate independent issues - Put unrelated problems on different cards so the discussion can address each one.
•
Let wording develop - Changes synchronize while authors type. They do not need to click away to share each revision.
•
Check participation - Use the current-viewer capsule to see who is present, and invite quieter contributors. The card author remains visible after the session even when that person has left.

Cards are attributable, not anonymous. Only their authors can change the wording or move them, so ask for a correction rather than attempting to edit someone else's contribution.

Discuss What the Cards Mean

Read across the observation columns and look for connected causes. Ask what happened, why it mattered, and what the team should repeat or change. Reactions can acknowledge a shared experience without filling the board with duplicate cards.

To react, open a card's menu with a secondary click or mobile long press, choose Add Reaction, and select an emoji. Reactions shows the people behind the responses. These controls depend on reaction permissions in the area.

Reactions are not a voting phase. A popular card is a useful discussion signal, but it does not automatically become the group's highest-priority action. Confirm the choice in conversation.

If an author needs to correct a recent edit, they can use Undo entry change or Redo entry change when available, or the usual undo/redo shortcuts while editing the card.

Turn an Observation into a Next Step

•
Agree on a concrete change - Replace vague aspirations with a behavior the team can recognize. Test the handoff checklist before Friday's review gives the group a clearer checkpoint than Improve communication.
•
Move or preserve the observation - The author can use Move to Action Items from the card menu and revise the wording. If the original problem should remain visible, add a separate action card instead.
•
Name responsibility in the wording - Add a person's name and an agreed checkpoint where useful. These are plain card text, so confirm that the person accepts the task.
•
Create tracked work when needed - Add the commitment to Goals if it needs assignment, status, or ongoing follow-up. A retrospective card does not create or update a Goal automatically.

Read the proposed actions aloud. A small set of understood commitments is easier to act on than a long list of ambitions.

Keep the Longer Discussion Connected

Use Comments for questions that should remain with the retrospective. Use the linked Article for background or a fuller summary through its normal content-editing controls. On desktop, these tools open beside the board so participants can return to the cards easily.

The Article starts as a draft. Completing this session does not publish it or create a feed post. See Linked Context and Meetings for the surrounding content and meeting controls.

Confirm the Shared Result

•
Wait for saved changes - Check the board's save status. In a standalone board, Ctrl+S or Cmd+S requests saving for your cards.
•
Check with another viewer - Confirm that the agreed wording and column placement are visible to someone else, especially after the final round of edits.
•
Resolve notices - If synchronization is interrupted, use Retry synchronization from the affected card's menu. Follow any retained-entry recovery prompt before treating that work as saved; Cards and Participation explains the choices.
•
Confirm the next review - Agree where the action items will be tracked and when the team will check their progress.

There is no finish or lock button. Leave through the app or meeting navigation once the group is ready. Reopen the same retrospective later to review the saved record or let authors refine their own cards.


Visual Space

4 Followers

Meet fellow creators and transform bright ideas into real projects ✦✦✦ or just geek out for the fun of it 😊

Visual Space is built for projects like this—where creators collaborate, organize goals, and grow communities around real work.