Objectives are where your team’s goals live, so the work coming out of retros has something to point at. An objective is the outcome you want; its key results are how you’ll know you got there.
Objectives and key results
Create one from Objectives → New Objective: a Title, an optional Description, and an owner. An objective moves through Draft → Active → Completed, and can be Archived. Filter the list by status to focus on what’s live.
Each objective holds one or more key results — the measurable part. A key result has a title, a target value, a current value, and a unit (a count by default). Its own status is On track, At risk, or Off track, shown as a colored dot so a glance tells you where each one stands.
Progress
Progress is computed, not hand-set: each key result’s progress is its current value against its target, and an objective’s progress is the average across its key results. Update a key result’s current value and both bars move. Some key results can pull their current value from a connected data source on a schedule, so the number stays current without manual entry.
Connecting retros to outcomes
This is where objectives earn their place in the loop. When you create an action item — on the retro board or directly — you can link it to a key result. That ties a specific commitment from a retro to the outcome it’s meant to move, so “what did we actually do about this goal?” has an answer you can point at.
Where it fits
Objectives are org-level, reachable from the sidebar’s Workspace section. They give retro output a destination: signals surface friction, retros turn it into commitments, and those commitments ladder up to the key results you’re trying to move. See Running a retro and Action items for the other end of that thread.