Home | Visual Space - Page 16

Use this walkthrough to turn an empty Whiteboard into a compact visual plan that another person can understand at a glance. You will create a clear title, decisions, tasks, a connected flow, and freehand review marks, then reorganize the result and reopen the board to confirm that the working canvas returned.

Retrospectives gives a team one persistent place to reflect on recent work, recognize what helped, name what should change, and turn the discussion into concrete follow-ups. It is useful after a sprint, project phase, event, incident, or any shared effort that deserves a deliberate pause before the team moves on.

A retrospective is more than the cards currently on screen. Every board is paired with a draft Article and its Comments, giving the team a durable place for background and discussion. The same board can also become a temporary live-app feed during an activity meeting without turning into a separate meeting-only copy.

Retrospectives helps teams pause, reflect, and turn shared feedback into practical follow-up. Start with the overview, understand how cards and linked context behave, or follow a complete journey from board creation through a finished team conversation.

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).

Assignees, color tags, activity labels, filters, and search add structure to a Goals workspace without changing what a goal is. The same goal keeps its article, discussion, reference, status, and board or backlog placement; these organizing details simply make responsibility and context easier to see.

Goals helps a community turn shared ideas into visible, organized work. Use this guide to understand the planning model, choose the right surface, or follow a complete workflow from creation through completion.

Goals gives a community a shared place to turn ideas into visible work. It is a lightweight planning layer for a space: structured enough to show what matters and who is helping, but deliberately less formal than a company project tracker. Each goal combines two useful shapes. On the board it is a compact card that can move through the community's workflow. Open it, and it becomes a full article with the context, discussion, and supporting content needed to help someone understand the work and c

Goal references give each goal a readable label that is easy to recognize on a board and easy to share in Chat. A label such as `VS-42` combines a space's goal key with the goal's number in that space. The label is a convenient name, not a fragile link. When someone selects a goal through the Chat picker, the shared reference continues to follow that intended goal even if its visible label later changes.

Completed Goals keeps finished work available as a record of progress after it no longer needs space on the active board. It is the second stage of completion: first a goal reaches a `Done` category, then a manager may clear that column into history without deleting the goal or its article.