OKRs and goals
Objectives and key resultsokrs.html
Tasks are what you are doing this week. OKRs — objectives and key results, sometimes just called goals or targets — are what all that work is supposed to add up to by the end of the quarter. The OKR page is where a team writes those down and watches them move.
New here?
This page covers everything. If you just want the core loop, read the two-minute version first.
Open it from OKRs in the navigation strip at the top of every page, between Team and Events. (Events only appears for people who have access to it.) It sits there because it is the same product, not a separate one: the same sign-in, the same team, the same people. It is also one of the four places you can choose to land on when you sign in.
My Work, the first entry in that strip, opens a short menu with My team
board and My OKRs, plus Help at the foot. My OKRs lands on this
page with the Mine chip lit — Your role set to All mine — so you arrive at the objectives you are on
the hook for or contribute to rather than the whole team's board. The plain OKRs entry
keeps the role you last used. Press Mine again, or choose Anyone under Your role
in Filter…, and the rest of the team's objectives come back. Arriving this way saves nothing,
and the ?mine=1 part of the address is dropped once it has been used.
All mine is deliberately wider than “objectives with my name in the owner box”. An objective counts as yours when any of these is true:
- you own the objective;
- you own one of its key results;
- you are listed as a collaborator on the objective;
- you are listed as a collaborator on one of its key results.
An objective you own counts even before it has a single key result, and that is not an accident of the quarter you are looking at: an objective you own that has no key results and is not placed in a quarter (its period was left as Spans quarters) is shown whatever quarter is selected, with “Not placed in a quarter” on its line, as long as Your role is not Anyone. With Anyone the team’s period stays exact. On the Overview, whose grid has a column for each quarter, a line names such objectives instead. On My key results they have their own rows: see below.
Key results that have been archived do not count. Owner and Collaborator in the same Your role control (in Filter…) narrow the list the same way, one at a time. If My OKRs is empty, that is an answer rather than a fault: the board says so, tells you which filter is responsible, and offers Clear filters to show everything.
A team admin has to switch OKRs on first
OKRs are off by default. Until a team admin turns them on there is no OKRs button anywhere and the rest of the app is exactly as it always was — nothing to notice and nothing to explain.
To turn them on: open Team, then Team Settings in the menu under your initials — or Actions → Board settings… in the team board’s view row. Switch on Objectives and key results, either in the first card on the OKRs tab or in its card on the Teams tab (they are the same switch). The entry appears straight away, with no reload.
Switching it off again hides the page but deletes nothing. Turn it back on and every objective, key result and check-in is still there.
OKRs belong to a team
If you are not on a team yet the page says so and offers a way back. Ask an administrator to add you.
Being on the team is not the same as having OKR access
Team membership does not automatically grant OKR access. Team Admins have it automatically; other Team members must be explicitly granted access through Team Settings → OKRs → Manage OKR access…. Members selected there can view and interact with Objectives and Key Results for the team — check-ins and comments included. Members who are not selected do not see the OKRs entry in their navigation for that team. OKR access is managed separately for each team.
New OKR access defaults to deny for normal Team members until explicitly assigned — so a Team that has used OKRs for months can still show nobody with explicit access the first time an admin opens that tab. That is expected: every Team Admin still has access regardless. If you cannot find OKRs in your navigation even though a team admin says it is switched on, this is almost always why — ask them to add you from that same tab.
The OKRs entry when your team has not switched them on
The OKRs entry is always in the navigation — on Tasks, Notes, Calendar, Team and OKRs alike, and in the View strip on the admin console. OKRs are off until a team admin turns them on, and while they are off the entry takes you to the setting that turns them on rather than to the page: Team settings › Team › Objectives and key results, with the switch already in front of you.
If you are a team admin, flip it and the entry starts opening the OKR page instead. If you are not, you will see the pane without that row — it is a team admin's setting — and you now know exactly what to ask for.
Whose OKRs you are looking at
Below the suite’s own navigation the OKR page has two rows. The view row holds, from the left, the team (only when you are on more than one team), List | Kanban, the three tabs Overview, Objectives and My key results — each with how many it holds, and the arrow keys move between them — the live label described below, then Actions and Customize. Under it the Focus strip counts what you are looking at and holds the tools: New objective (on every tab, Overview included), Period and Current quarter, the Organize link (a one-line summary of how the list is arranged, for example By area · Kanban · Grouped, which opens Customize at Organize), Filter…, Clear filters and Re-evaluate. The strip is described in The Focus strip: the figures and Board at a glance. There is no title band: the navigation already names the page. Actions holds the two reports and OKR Settings (see Exporting the board, or printing it and OKR Settings), and there is no settings gear. Sort, Hide completed and the pin are in Customize (see below); help is in the menu under your initials, and the ? key opens this manual. Your role and Collaborators are in Filter…, and the Mine chip in the strip is Your role in one press.
List | Kanban in the view row, and Organize in the strip. List | Kanban is a pair of icons beside the team (from a wide window, 1440 pixels, it shows the words too): the lines are List, the columns are Kanban, and the lit one is what you are looking at. On Overview, which has one layout, it is dimmed, neither icon is lit, and it says why rather than disappearing. There is no separate Group by button: the Organize link in the strip is the one door to grouping, and it opens Customize at Organize, where Group objectives by offers Area or Status (on My key results, Group key results by offers Status, Objective or Area). With the keyboard, Tab moves from one List | Kanban icon to the other without switching, and Enter or Space switches, as on the Tasks page’s List | Calendar. They are the same settings as the rows in Customize, and an open panel follows when you use the bar. Like those rows they last for this tab’s session and are not saved to your account.
If you used this board before, these two were called Row and Column. It is the same board under a new name — nothing about how it works changed, and if you had already chosen one, you do not need to set it again: your stored choice still applies under its new label.
Colleagues' changes appear on their own when live editing is on. The OKR header then shows a blue, glowing Live · 2 here label in the view row, just before Actions, with the avatars of the people looking at the same team’s OKRs; while nobody else is there it reads Live editing ready in plain gray. It starts only while someone else has them open: press Live editing ready to check now instead of waiting. If someone else has the OKRs open you go live straight away; if not it says Just you here, and nothing opens while you are alone. Organization owners find Live editing settings… under the small arrow beside the label. An objective or key result a colleague changes, adds or archives, a new check-in, a progress value and a Kanban move all appear within a couple of seconds, and the changed rows pulse once. The update waits while you have a dialog or menu open, hold a progress bar or are typing, and an open objective is never overwritten: its dialog says a colleague changed these OKRs, and your save is checked against their version, so the first save wins. Press the label to see why live editing is off; while it is off, changes appear when you reload. While the label reads Live, the page does not refresh itself when you come back to the tab: live updates already keep it current. If the connection drops or live editing turns off, that refresh starts again straight away. If others have the OKRs open but your browser cannot open the live connection, the label turns amber and reads Live editing can’t connect: changes still save, it keeps trying while they are there, and pressing the label tries again now.
The page belongs to one team at a time — Northwind Digital in the picture below — and if you are on more than one team a Team dropdown sits at the start of the view row. Choosing another team replaces everything on the page: its objectives, key results, quarters and health thresholds, which are set once for the whole team. On one team there is no dropdown. The team you pick follows you between the apps for as long as the browser tab is open — switch team here, press Team, and you land on that team's board.
A new session starts where you usually work: your default team if you have set one, otherwise the first team you belong to, and the board you last had open on it. It is checked against your current memberships — if you have left a team since, the page falls back rather than refusing you. Set your default team in Settings → Workspace → Where you work.
The Focus strip: the figures and Board at a glance
The strip under the view row counts the objectives you are looking at — or, on My key results, your key results. From the left:
- The fold, Board at a glance (Glance on a narrow window). It is folded until you press it, and it remembers how you left it, on your account. Customize › Layout › Show Board at a glance is the same switch. Opened, it shows the breakdown: the ring with % on track or ahead beside it, the bar of the key results beneath this selection, Health uses your team’s thresholds with a See thresholds button, and a line naming the ladder — objective, key result, task. The figures themselves are always there, folded or not.
- The figures. In view counts everything the board is showing (it reads Overall while a filter narrows the list below it), then come the six health states — Behind, Slightly Behind, On Track, Ahead, Completed and Not Started — each count in its health color (a count of zero is gray). Each one is a button: press it to see only those, press it again, or press In view, to clear. Hover one to see how many key results sit under those objectives, in the quarters you have selected.
- Quick chips. Mine shows the work you own or collaborate on; it is the same as Your role → All mine in Filter…, and it stays lit while any role filter is on, so a role filter is never invisible. It is not offered on My key results, which is already only yours. Recently created keeps the objectives created today, by your own device’s clock.
- The tools, then, at the right: New objective, Period, Current quarter, Organize, Filter…, Clear filters (only while a filter is on) and Re-evaluate, which uses your own AI key. On a screen narrower than 1920 pixels they make room for the figures: every tool but New objective shows only its icon (point at it, or listen to it with a screen reader, for its name), and Period drops the word current.
Objectives, key results, and quarters
Three ideas, and it is worth being clear about which is which:
- An objective is the outcome you are going for. It is a sentence, not a number — "make the reporting pipeline something people trust".
- A key result is how you will know you got there. It is always a number that moves: from a start, to a target, by a date.
- A quarter — the app calls it a cycle — is the window. Every objective lives in exactly one, and you switch between them with the quarter dropdown.
An objective with no key results underneath it shows a gray no key results marker. That is deliberate: it is an intention nobody can check, and the app would rather say so than quietly show it as fine.
Objectives can also be filed under an area — whatever your team wants to call it. Areas are optional, and if you do not use them everything simply sits under "Unassigned".
Adding an objective, and its key results
Fields marked optional can be left empty — an objective with no owner is allowed.
- Choose the quarter you are planning in, from the dropdown at the top.
- Press New objective.
- Give it a title, and optionally a line about why it matters, an area, and an owner.
- Press Create & add key results. The objective is created and the key-result form opens straight onto it, so you do not have to find it again. (Create on its own just makes the objective.)
- Fill in the start, the target and where it is today. Measured in starts as Percent, which is what most measures are.
- Press Save & add another for the next one, as many times as you need, then Create on the last.
New objective
Make the reporting pipeline something people trust
Nobody re-checks a number they believe.
Add key result
Cut overnight pipeline failures from 14 to 2 a week
You can still press Add key result under an objective later — nothing about the old route has changed.
Typing a name to find an owner
The Owner box on both forms has a search field above it. Type any part of a name and the list narrows; press Enter and it picks the person if exactly one matches. If two people match it picks neither and says so — the same rule the rest of the product follows, because guessing between two Ashleys is worse than asking. Whoever is already selected stays selected while you search.
Three to five objectives a quarter is plenty. The page will hold as many as you like, but a list of thirty is a list nobody reads.
“This looks like it already exists”
Before a new objective is created, the title is checked against this team’s other active objectives in the same quarter. An exact match — same wording, give or take spacing and case — is caught instantly, with no AI assistant needed. If you have an assistant configured, a second, looser check runs quietly in the background and can also catch a goal worded differently — “Launch the DMS” against an existing “Complete and launch Harbor DMS”. It never holds up typing or pressing Create.
Either way you see the same dialog: the objective it thinks you are repeating, its owner, quarter and status, and — for the AI match — one sentence saying why. Continue anyway creates your objective exactly as typed; Go back (the default if you press Enter) returns you to the form untouched; View existing objective opens the match itself so you can check before deciding. Nothing is ever merged, edited or deleted on your behalf.
Importing straight from Profit.co
If your OKRs live in Profit.co, you do not have to prepare anything. Export from Profit.co, drop the file in exactly as it came — .xlsx or .csv, all of its columns — and this recognizes it and does the mapping for you. No renaming columns, no deleting the ones we do not need, no rebuilding the objective and key-result structure by hand.
- Open Settings → Bulk changes → Import from a CSV file and drop the export in.
- It says recognized as a Profit.co export and reads it. Nothing is written yet.
- Read the summary. It is written in plain English — how many objectives and key results the file holds, how many are new, how many already exist, how many will have missing information filled in, and how many need you to look at them.
- Open the detail to see, field by field, what is in this application now, what the file says, and what it would become — grouped New, Updated from the file and Unchanged, all closed by default (anything needing your attention is in a separate group, open by default).
- Press Accept & Import, or Cancel. Cancel writes nothing at all.
Importing next month's export over the top
Safe, and it is meant to be: every objective and key result remembers its Profit.co id, so a later export of the same OKRs finds the same records here. It adds what is new, fills in what was missing, and leaves alone anything you have already filled in yourself. Some Profit.co exports have no ID columns — those records are matched on name instead, so a rename is not survivable: renaming an objective or key result in the spreadsheet creates a new one rather than updating the old.
Where the file disagrees with what is here, the file wins for the owner, the description, and a key result’s unit, metric name, direction, limits and dates. Your area and quarter are never moved: they are filled in when empty and otherwise left exactly as you set them. It will not touch the numbers on a key result — the current value, start and target are your check-ins, and no import may move them — and it will not delete anything just because it is missing from the file.
When the file names somebody, an area or a quarter you do not have
- An owner who is not on this team comes in unassigned, with a comment recording who owned it in Profit.co. Do not import this person leaves the name out of that comment entirely — the rows still come in.
- A tag that matches no portfolio area, a retired area, or no tag at all files the objective with no area. It appears under Unassigned in Overview, and the import never creates an area of its own.
- More than one person named on a row: the first one on this team becomes owner; everyone else on this team is recorded as a contributor — a record only, granting no access.
- A quarter you do not have: the quarter is added.
When the export does not look quite the same — a column no longer matching a name this recognizes — and you have an AI assistant configured, it is asked what that column is, from the heading and a few example values. You do not need an AI assistant for an ordinary export. Where it cannot be certain — two objectives that could both match, or a key result whose objective cannot be worked out — that row is set aside and named in the summary rather than guessed at. Everything else still imports.
If the file carries an OKR Level or OKR Context column, the preview offers it as a scope filter — every value found, ticked (included) by default, so unticking one leaves those rows out of this import only; the file itself is untouched.
Import history, and running one again
Every import is recorded on the server, so it is the team’s history rather than your browser's — everyone on the team sees the same list — from Import history: when it ran, who ran it, which file, and what it did. The rows that could not be imported are listed so you can enter them by hand, each showing the objective and key result names, the owner exactly as the file wrote it, the quarter and the reason, downloadable as a CSV.
Running an earlier import again
Re-run does not repeat what already happened — it takes the same data and works out what it would mean now, so a row set aside then may import cleanly today because the team or its areas have changed. It always creates a new import; the old one stays as the record of what happened that day.
Undoing an import
Open Import history, find the import, and press Undo this import. That does not delete anything — it shows exactly what would go and stay before asking. Only the person who ran an import can reverse it (a system administrator can too). It removes only what that import created, and reverts anything it merely changed. It will not delete work you have done since: a check-in, an edit, a comment or a linked task on an imported key result survives. It does not bring back the numbers people typed — so undo only when you mean it. A reversed import stays in the history marked Reverted.
Importing a quarter from a spreadsheet
For OKRs already planned in any ordinary spreadsheet. Open OKR Settings → Bulk changes → Import from CSV…, under Import from a CSV file.
Running the import needs a Super Team Admin
Anybody who can see the tab can open the importer, choose a file and read the preview; the write itself is refused by the database below Super Team Admin. Importing a file of OKRs is a Super Team Admin action, while importing tasks onto a board is the board administrator’s and importing people onto a team is an ordinary team admin’s. See Team roles and Permissions by role.
- Press Download a template CSV, pre-filled with your team’s own area, quarter and owner.
- Replace the example rows. One row per key result — repeat the objective’s title across its rows to group them; a row with no key result creates the objective alone.
- Drag the file in, or press Choose a file. .xlsx or .csv, recognized by what is inside it rather than its name.
- Correct any column the headings did not already settle, or press Suggest a mapping with AI if you have an assistant configured.
- Check the three counts — ready, needs attention, cannot be imported — then press Import.
Common reasons a row cannot be imported: the owner is not on this team (comes in unassigned with a comment instead); this team has no quarter called… (add it under OKR Settings → Quarters); or a key result needs a target.
Importing the same file twice
It will not build a second board. An objective whose title already exists in that quarter is matched to it, and only its new key results are added — those rows are marked needs attention until you tick Import the rows that need attention too.
Explain what an imported measure means
Some exports state every key result as a bare 0–100 percentage with no metric name, unit or direction. With an AI assistant configured, the preview offers Read what these measures mean: it reads each distinct title and proposes a metric, unit, direction and, where the title states one, a starting and target number. A field already set is never overwritten, and the key result’s actual numbers are never moved. Nothing is written until Accept & Import.
Every import is recorded; see Import history, and running one again to read what any of them did or take one back off the board.
What an objective's line tells you
Under the title: the area, the owner, the quarter or quarters it covers (worked out from its measures — one with measures in Q3 and Q4 reads 2026 Q3–Q4), and how many key results it has. On the right, its status and percentage. Its outline takes its color from that same status — the same color as the dot beside its title.
The objective's own actions
Open an objective and the bordered Objective actions panel is the first thing under its title, open by default, with the key results in their own cards below — no scrolling past every key result to edit the objective. It is the same panel in List and in Kanban's card dialog. Press its heading (or Space) to fold it to a one-line strip when you want to focus on the key results; it opens again each time you open the objective. A key result you add scrolls into view.
| Button | What it does |
|---|---|
| Add key result | Opens the key-result form already pointed at this objective — the same form Create & add key results opens when you first create one. |
| Edit objective | Title, owner, area, quarter, contributors and the line about why it matters. |
| Comments | Discussion on the objective itself — the same comment box every other Comments button opens, mentions included. |
| History | What changed on this objective, and when. |
| Copy link | Copies a link straight to this objective — pasted into a message, it opens OKRs and takes the reader directly to it, the same way a copied task link opens Tasks on that task. The same button sits on every key result's own action row, for a link to that measure specifically. |
History lists title, owner, state, area and quarter changes, which key results joined or left the roll-up, every check-in on those key results, and any date that moved — each line names who made the change and an exact, zoned timestamp. Entries are newest first, grouped under the day they happened. It reads “No history recorded yet” for an objective with nothing recorded.
Created by sits at the end of the buttons row (under the heading when the window is narrow). The objective's Insight has a row of its own underneath, across the full width of the panel: its heading line holds the stale note when the figures have changed, when it was written, and Regenerate (or Write insight when there is none yet). The text shows its first three lines; when there is more, Show full insight opens the rest and Show less closes it again. It stays open while you work on the objective and shuts the next time you open it. Folded, the strip still says who filed it and whether there is an insight.
Private goals
An objective is Team or Private. Team is how every objective starts: everyone with OKR access on the team can see it. Private limits it, and everything under it — its key results, check-ins, comments, history and insight — to the people it involves. Use it for goals you want to work on with a few people, or to share progress with your manager, before or instead of showing the whole team.
Who can see a private goal
- The people it involves: its owner, whoever created it, the owner of any of its key results, and the collaborators on the objective or on any of its key results.
- Team administrators, Super Team Admins and organization owners, who can see every objective on their team and still can, without being added. The people who run the product can also see it in the Admin Console, where it carries a Private tag.
- Nobody else. Everyone else with OKR access sees nothing: no title, no count and no gap in a list or a total.
Private means private from your colleagues, not from administrators, so the dialogs below say so each time.
Making a goal private, or putting it back
When you create an objective, Who can see this offers Team (the default) or Private. On an objective that already exists, open it and press Make private in its Objective actions; once it is private the same button reads Make team. Each press asks first. Make this objective private? lists who keeps access and says that everyone else stops seeing it, apart from team administrators and organization owners; it also says how many linked tasks belong to people outside, who will see only “A private objective” on those tasks. Make this objective visible to the team? says that everyone with OKR access on the team will see it, its key results, comments and history.
Only the owner or the creator can change this. Collaborators, key-result owners and even team administrators do not get the button, and the server refuses them if they try another way, because who else sees a goal is the decision of the person it belongs to. Someone who made themselves the owner cannot take a team objective private, and an administrator who made themselves the owner cannot switch it either way; the creator, or an owner somebody else chose, can. The change shows in the objective’s History.
Who it is shared with
Share it in Edit objective, with the same Collaborators field as any objective; its hint reads “Collaborators can see and work on this private objective.” Add your manager or anyone else you want to share progress with. The picker lists only people who have OKR access on this team, because someone without it could never open the goal; naming anyone else says “Only people with OKR access on this team can be added.” A collaborator on one key result can see the whole objective.
- Only the owner or the creator can add or remove collaborators on a private objective, on the objective or on any of its key results. Team administrators do not.
- The same two people are the only ones who can give a key result to someone who is not already one of the people involved, or move a key result into or out of the objective. Anyone else is told that only the owner or creator can do that.
- Someone who owns a key result stays among the people involved even when you take them off the list; reassign the key result first.
- Whoever is added is told, once: a notice in Messages and, under OKR updates, an email, “… shared a private objective with you”. Nothing is sent when someone is removed. Later updates to a private objective, emails and mentions included, reach only people who can see it.
Where private goals appear
When you can see at least one, the board splits in two: Team objectives, then Private goals I can see, each with its own count and a small lock. Grouping, sorting, filters, folding and search apply inside each section, and folding a group in one does not fold it in the other. Every private goal carries a Private chip (a lock and the word) beside its name and a tinted edge down its left side that continues through its key results, in the list, on the Kanban card, in the objective dialog, in the Overview's private list and on the objective link under each key result in My key results; on a narrow screen the chip shrinks to the lock. Global search marks private results with the same lock. With none to show, the board is exactly as it was.
Goals shown: All, Team or Private, in one press
Three small icons sit beside List | Kanban in the view row, on Overview, Objectives and My key results: the people icon is Team objectives only, the lock is Private goals only (the ones you can see), and the group icon is All goals. They are icons at every width. Hold the pointer over one (or focus it) and its tooltip gives the count, for example “Private goals only: the ones you can see, 3”; a screen reader reads the same. The count is of the goals in this period that match your Area, Owner, Your role and search; Hide completed and a status you picked are not applied to it. The lit icon is the one in force. With the keyboard, Tab moves from one icon to the next without choosing, and Enter or Space chooses, as on List | Kanban. The choice combines with every other filter: Mine with Private is your own private goals. It lasts for this tab’s session, is kept with the rest of how you left the board, and is not saved to your account. Clear filters puts it back to All and keeps your period and sort.
On the Overview the team figures are unchanged under All and Team; under All one muted line says how many private goals you can see are “not counted here” with Show them, which chooses Private. Under Private the Overview shows a panel headed Private goals with the lock: a short list of those goals with a status dot, their own figures in the strip, and the words that they are not counted in team figures. They are never added to a team number. With Private chosen and none to show, you are told so: “No private goals yet”, with Create a private goal, which opens the ordinary new objective form with Who can see this already set to Private. With Team chosen and nothing matching, the list says “No team objectives match” and names Goals shown: Team only.
Team figures count team objectives only
A private goal never counts in a figure the whole team compares: the headline and status cards, the area and quarter summaries and the period totals, Signals, the quarter digest and the printed board document. So two people always read the same team numbers, and a screenshot of the Overview cannot carry a private goal. When you can see one, the Overview says “Team figures count team objectives only”. A private goal does count where the view is yours: the objectives list, My key results, one person’s report card, and the spreadsheet export, which has a Visibility column (the CSV import reads the same column: Team or Private, blank means Team, and it never changes an objective that already exists). AI insights are written about a private goal only for people who can see it.
Private goals in a person’s report card
The report includes the private goals the person running it can see. You can run it for yourself, and a team administrator or organization owner can run it for anyone on the team, so in every case it shows all of that person’s private goals, each marked with a small lock and none explained away in a footnote.
Tasks and checklists linked to a private goal
Linking a task to a goal does not make the goal visible to the task’s owner. If you cannot see the objective, your task’s Supports card shows “A private objective” with a lock and nothing else — no title, owner or progress — and a Remove link button, and the same line is what the task’s print-out and its AI summary say. A checklist item linked to an objective or key result you cannot reach reads “Objective unavailable” or “Key result unavailable”: STRIDE cannot tell a private goal from a deleted one, and says nothing that would let you.
Administrators, deleting and closing
In the Admin Console, the OKRs section lists every objective with its real title and a Private tag. A private objective belongs to its team like any other: deleting the team or closing the organization removes it with everything else, and the confirmation counts it.
Reading the health colors
An objective is a diamond and a key result is a circle, so you can tell the two apart at a glance while you are reading down a list. A task linked to a measure is a small square.
Every objective carries a colored marker. The color is not somebody's opinion — it is worked out from how far along you are compared with how far through the quarter it is, and it is expressed in days.
A key result is colored by its pace. Ahead, On track, Slightly behind and Behind color its bar and dot, with its status in words beside it. Not started and Completed stay a quiet gray, so color still means “look at this”.
If a key result is halfway to its target and the quarter is halfway through, it is on track. If the quarter is halfway through and you are a quarter of the way there, you are about three weeks behind the clock, and it turns amber.
| Color | What it means |
|---|---|
| Ahead | Further along than the calendar expects. |
| On Track | Where you should be, give or take a few days. |
| Slightly Behind | Adrift, but recoverable this quarter. |
| Behind | Far enough back that something has to change. |
| Completed | Reached its target, or marked complete. |
| Not Started | Nothing recorded yet, and there is still time. A measure sitting at zero with the quarter nearly gone is Behind, not Not Started — see below. |
| Not scored this quarter | The objective is filed in the quarter you are looking at, but all of its key results are in another one. There is nothing here to measure, so it is not measured — see below. |
“Not scored this quarter” is not a seventh health color
The six above are verdicts about how work is going. This one says the question does not apply here yet — you get it when an objective sits in the quarter you are filtering on but every one of its key results sits in a different quarter, which happens legitimately when you move an objective to next quarter and its measures stay where they were. Such an objective leaves the Not Started group entirely and appears in its own group at the bottom of the list, with a dash instead of a percentage. It is left out of the quarter's roll-up, so it does not drag the healthy percentage down. It is also not something to fix: if the measures belong in the other quarter, leave them there.
An objective's color is its average pace, and its number is its average progress
The marker on an objective is the average pace of the key results underneath it, banded. Three sailing and one stuck usually comes out as sailing, so a stuck measure is named by the count beside the objective — 1 behind, 2 slightly behind. Its percentage is a different question, and that one IS the average. Five measures at 75%, 30%, 1%, 0% and 25% make an objective at 26%. Only key results in the quarters you have selected count, in both. Archived key results are left out, and an objective with no key results shows — rather than 0%.
"Nothing recorded yet" runs out
A key result created this morning is Not Started, not Behind — calling it behind on day one teaches everyone to ignore the colors. But that only holds while there is still time. Once the quarter clock says it should have moved, a measure at zero is Behind, and an objective containing one says so even if its other measures are finished.
Changing where the bands fall
The scale the colors come from is one setting for the whole team, and you see it in OKR Settings → Health signal. The numbers on the handles are days from the quarter clock, not percentages — 0 means exactly on schedule, and a positive number means that many days late. Halfway through the quarter at 20% is about 27 days behind; the same 20% in the first week is ahead. The panel lists what each color covers as you move the handles.
Only Team admins change it. They set it in Team settings → OKRs, in the Health thresholds card: drag a handle, click anywhere on the track to move the nearest one, or use the arrow keys — Shift moves faster, Home and End jump to the ends. The colors update when you let go, for everyone on the team. Reset to defaults returns the team to the product’s own bands.
Everyone else sees the same scale read-only in Health signal, marked Set by your team’s admins. Admins get a Change in Team settings link there that opens the card. Because it is one setting rather than one each, the colors on your screen match your teammates’ exactly.
Writing a good key result
A key result needs three numbers: where it started, where it is now, and where it needs to get to. Pick a measured in type so it displays sensibly:
- Number — a count. Add a unit like "sites" or "customers" if it helps.
- Percent — shown with a % sign.
- Currency — shown as $2.5k or $3.2M.
- Done / not done — for the ones that either happened or did not.
The target can be lower than the start. "Reduce p95 latency from 800ms to 200ms" measures exactly the same way — progress is how far you have moved from the start toward the target, whichever direction that is.
Start and target have to differ, though. If they are the same there is nothing to measure, and the app will say so rather than show a meaningless bar.
Quarters and due dates
An objective sits in a quarter. Each key result has its own quarter, which starts as the objective's — an objective set in Q3 often has measures landing in Q4, and forcing them all into one quarter makes every roll-up wrong.
The due date is filled in from the quarter: pick 2026 Q3 and it becomes 30 September 2026. Change the quarter and the date moves with it. If you set a date yourself, it is kept — changing the quarter will not overwrite a date you chose deliberately.
A key result cannot be saved without a due date. Without one there is nothing for the health colors to measure against, so it could never be behind.
The quarters you select decide which key results count. A key result counts when its own quarter is selected; its due date does not come into it. Progress, pace, color, the count beside an objective, the digest and the Overview all use that same set.
Moving an objective to a different quarter
Because a key result carries its own quarter, changing the objective's quarter does not move its measures with it. So when you change it and there are key results sitting in the quarter you are leaving, the page asks “Move key results too?” before saving.
The dialog names the real quarters and counts the real measures, with Move them to the new quarter chosen for you — though Leave them is a real answer too: a measure you genuinely finished in the old quarter should stay there as history. Archived measures are never counted or moved.
If you choose Leave them and every measure ends up in a different quarter from the objective, the objective will read Not scored this quarter in the quarter it now sits in. That is expected, not a problem — see Reading the health colors.
Checking in on progress
Press Check in on any key result. Enter where the number is now, optionally say how confident you feel and what changed, and save.
A check-in does two things: it moves the key result, and it leaves a dated note of who reported what. That history is the part people value next quarter, when someone asks why a number moved the way it did.
The box opens with your last confidence selected, and shows the pace beside it for reference only (Ahead, 29 days ahead). “Expected by today” follows the key result's own quarter, even under All quarters.
You can correct a check-in you posted, until its quarter ends. Press Edit on your own check-in in the history to change its value, confidence or note; its date stays the same. An edited check-in is marked edited, and the original is kept on record. If it is the latest check-in, the key result moves to the corrected value. Only the person who posted a check-in can edit it. A corrected check-in still needs a value: leave it empty and Save says A check-in needs a number.
Seeing at a glance who has checked in
Beside a key result's numbers — and beside an objective's status and percentage — a quiet Check-in 2 says how many check-ins there have been. An objective's number is the total across its key results, since a check-in always belongs to a measure rather than to the objective itself.
It counts the quarters you are looking at, not all of history. Filter to 2026 Q3 and it counts the check-ins recorded during Q3; add Q2 and it counts both. A check-in belongs to the quarter it was recorded in, which is not always the quarter its key result is planned for — a measure planned for Q4 that somebody updated in September counts toward Q3. Nothing is shown when the count is zero. Press it and it takes you to the check-ins: on a key result it opens that measure's details and expands its check-in history; on an objective it opens the objective and expands every key result that has check-ins in the period.
Who is emailed about an update
When an objective or key result gets a check-in, a change to its status, date, cycle, title, area or owner, a key result added or removed, or a comment, its owner and contributors are emailed, and the owner of the parent objective hears about its key results.
Imported check-ins send nothing. The person who makes a change is never emailed about it.
Telling somebody about it
Type @ in the note to mention anybody on any of your teams — they get it in their Messages panel, with a count on the button, the same inbox that carries task mentions. Start typing a name and the list narrows; arrow keys move, Enter picks. The @ works in an objective's or a key result's Comments too, and an @mention in one of those comments emails the person named, like a mention on a task.
A check-in that mentions somebody also posts its note as a comment, and the box tells you so before you save. That is how the people you named have something to open: a check-in is a number and a date, and the comment thread is where a remark can actually be read. A check-in that mentions nobody stays a check-in and posts nothing.
You can mention anybody in the team that owns the OKR, and nobody else — that is who can read its comments. Somebody in another of your teams is not offered, because a message they could never open is not a message.
The comment box is at the top of the Comments on an objective or key result. Type at the top; newest first; scroll down for older. Post stays in the dialog's footer.
Reacting to a comment
A comment on an objective or a key result takes the same three reactions as a task comment: 🙌 High five, 👍 Thumbs up and ❤️ Heart. You have one per comment, pressing it again takes it back, and a reaction notifies nobody. Reacting counts as reading for you: it clears your Messages mention for that comment and any earlier one in the same discussion. Anybody on the team who can read the objective can react to its comments.
Formatting a comment
The comment box has formatting controls above it — the same bar the task and note comment boxes have: bold, italic, underline and strikethrough, bulleted and numbered lists, text size, color and highlight, a link, clear formatting, and undo and redo. It is on the Comments box of an objective and of a key result. On a narrow window the controls that do not fit fold into More formatting rather than disappearing. Comments written before the bar arrived read exactly as they always did. A comment is still capped at 4,000 characters, and the cap counts what you typed rather than the formatting around it.
The check-in note is deliberately plain. "What changed" on a check-in takes text only, since it sits beside the number in the history rather than being a message in a conversation. Mentioning somebody in one still posts it as a comment.
Moving the bar offers a check-in for you. Drag a measure or type its number and it saves at once; a short check-in box then appears underneath asking what changed. Write a sentence and it joins the history, exactly as pressing Check in does.
Dismissing that box does not undo your change
They are two separate things. The new value is already saved by the time the box appears — closing it only skips the note. The same is true if saving the note fails: the number stays where you put it.
Changing the number without a note is sometimes exactly right — fixing a typo, for instance. It simply leaves no trail, which is what the note is for.
Connecting tasks to a key result
This is what keeps OKRs from becoming a separate world. Open a key result, press Linked work, then Link a task, and pick from your own open tasks. The key result then shows how much real work is pointing at it, and each linked task opens in its own editor right over the OKR page — a team task in its board’s editor, any other task in the task editor — without leaving OKRs.
Only tasks you own can be linked. That is deliberate — otherwise anyone could attach somebody else's private task to a shared objective and put it in front of the whole team.
Unlinking removes the connection only. It never deletes, completes or changes the task itself.
The Overview dashboard
The Overview tab steps back from this quarter to the whole picture. Everything on it is clickable and takes you into the objectives list scoped to exactly what you clicked.
- OKRs by area, by quarter — a grid of areas against quarters showing average progress per cell. The ring beside each figure draws the mix of health beneath the cell, so a cell can be early in its progress while what exists is on track. Future quarters show how much is planned instead. A cell judges each objective exactly as the Objectives list does for that quarter: one whose key results all sit in another quarter reads Not scored this quarter there, a key result checked in at zero is judged on its pace rather than read as not started, and an archived key result counts in no column. See The grid shows the period you have chosen and Narrowing the grid further.
- Readiness — what next quarter looks like today: drafted, without key results, already underway, and how many areas are represented. Objectives planned, Objectives without key results and Already underway each open the list narrowed to exactly what they counted, with a Clear control to back out. Key results drafted counts measures rather than objectives, so it opens the same planned-objectives list with a note explaining why. Areas represented switches the list to Group by area instead of filtering it.
- Earlier quarters — a banner listing work that rolled past its quarter without anyone deciding to finish it, move it, or drop it.
- Data hygiene — small clean-ups that keep the other numbers honest. This card disappears when there is nothing to fix, which is the point.
The grid shows the period you have chosen
The filters at the top of the page decide what this grid is made of. Set Period to two quarters and the grid has two columns — the quarters you are not looking at are not drawn at all. Pick an Area and it has one row, that area’s, and the All areas total underneath is dropped. Leave either one alone and every quarter, or every area, is drawn — the grid is the filter, laid out as a table, which is what makes it worth sharing.
Work outside the period is counted, not silently dropped. A line under the chooser says how many objectives sit outside the quarters you have selected, with a Show every quarter button that widens the period.
The blue is the status you are hunting
Press one of the snapshot tiles — 11 behind, 1 slightly behind — and the squares holding that work go blue, so you can see at a glance where the eleven are. Press the tile again to clear it. A status cannot be answered by dropping a column the way a quarter can, so it is shown by color instead. With no status chosen there is no blue at all, because every square on the grid is already in your filter — that is what the columns mean. An empty square never goes blue even while hunting a status, the quarter containing today is still labeled now (a label, not a selection), and if none of the squares on screen holds the status you picked, the card says so. Nothing is hidden by the color: every square keeps its percentage and its status ring, and the tooltip says in words what the blue means — it is never color alone.
Narrowing the grid further, just for a screenshot
Inside the card, a second control — Areas and quarters shown — gives you a chip for every area and every quarter the filters above have left. Press one to take that row or column out of the grid; press it again to bring it back. Why both? Changing the Period at the top re-narrows the objectives list, the totals and the digest with it — you lose the view you were working in; this one changes only the picture — “I am working in Q2 and Q3 and I want to screenshot Q3 on its own” is a sentence only this control can say. It cannot widen anything. It only ever narrows what Period has already left in. For that, change Period, or press Show every quarter above.
- Where the filter above has already decided, this one steps aside. Pick a single quarter or area at the top and there is nothing left to choose here.
- Take every chip off an axis and the whole axis comes back — you can never end up looking at an empty grid.
- The totals row renames itself All areas or Selected areas, and its figure totals only the rows you can actually see. Narrow to one row and the total is dropped, because a total of one row is that row written twice.
- All areas, All quarters and Show all areas and quarters put one or both axes back; none of them appears while there is nothing to undo.
Nothing here is remembered. Refresh the page and the grid is back to the full period again — the Period and Area filters at the top are remembered, as they always were; that is the difference between an arrangement and a screenshot.
The wheel is a filter
The ring in the Board at a glance fold is not just a picture. Click a colored segment and the list filters to that status — the same as pressing the matching figure in the strip. Click the segment again to clear it, or click the number in the middle to clear the status filter and see everything again. It clears only the status: the area, owner and quarter you had chosen stay as they were. It works the same in List and Kanban, and from the keyboard — tab to a segment and press Enter.
Shortening the list: finished work, and your own
Hide completed — Customize › Show and hide › Hide finished objectives — takes every finished objective out of the list. Your role (in Filter…, or the Mine chip for owner or collaborator) leaves only the objectives that match it. Owner means you own the objective or one of its key results — deliberately both, since an objective owned by a director with its measures spread across the team would otherwise be missing from a list of “objectives I own”. Collaborator means you are listed as a collaborator on the objective or on one of its key results. A key result somebody archived does not count. Collaborators, just below Owner in Filter…, keeps only the objectives those people contribute to; ticking several people keeps any of them. All of these work the same in List and in Kanban, and on Overview. (Your role still brings each objective’s teammates’ key results along with it; My key results lists only yours.) They are remembered per team — still set after a refresh, and on the next visit, and Clear filters lifts them. Picking people in Owner or Collaborators does not change Your role: the role means “me”, the lists mean “these people”. Clear filters lifts every filter and keeps the quarter (Period) and the sort. They shorten the list and nothing else: the totals in the strip — the figures and the ring, Completed among them — keep counting everything, and the area, owner and quarter dropdowns keep offering everything too. Press the Completed figure to see the finished ones anyway: asking for them outright wins over the checkbox.
My key results: just the ones you update
Your role: All mine keeps every objective that has something of yours in it — which means the objective still comes with your teammates’ key results, and nothing on that list shows only yours. My key results, the third tab beside Overview and Objectives, is the list for that: one card (or one table row) for every key result you own or contribute to, with a Check in button on each, and nothing to open first. The tab carries a count of how many you have, so it is one press away from Objectives whichever Your role is on.
An objective you own that has no key results yet has a row too, in a panel above the list headed No key results yet: its title (press it to open the objective), your role, “Not placed in a quarter” when that is so, and an Add key result button that opens the key result form on it. These rows are not scored, so they are not in the donut or the six figures, and the tab’s hint counts them (“and 2 objectives without any”). An objective you only collaborate on that has none shows without the button, under All or Collaborator. Because you own something, this view never tells you the board’s work “belongs to teammates”. Goals shown (see Private goals) filters this list too.
A card shows that key result’s own status, where it stands against its target, its due date (Overdue when it has passed), how many check-ins it has and when it was last checked in on, and the objective it belongs to — press that line to open the objective, with your own key results marked down its edge. A chip says whether you are the Owner or a Collaborator; for the second it also names whoever owns it. Check in opens the same dialog a key result has everywhere else — the value, the confidence, the note, the history underneath — and the card has the new figure the moment you press Record check-in, without a refresh.
- All, Owner, Collaborator narrows the list to the key results you own, or to the ones you only contribute to.
- Group by (the Organize link in the strip, or Customize › Organize › Group key results by) has three choices here: Status, Objective or Area. Layout (List | Kanban in the view row, or Customize › Layout › Show objectives as) is Kanban (a column per group, a card per key result) or List, a table whose column headings sort it and which scrolls sideways inside its own frame on a narrow screen.
- The strip above counts your key results — the six health figures, the ring in its fold, and how many are yours against how many you contribute to — and the figures narrow the list the way they do on Objectives.
- Hide finished (Customize › Show and hide) is the same switch as on Objectives, off until you tick it, and each key result is judged against its own quarter. Period and Area apply exactly as they do on Objectives. Search and Owner are about the key result itself here: type part of a key result’s title (or its owner’s name) and only the key results that match are listed, not the other key results under the same objective; pick somebody under Owner and you see the key results that person owns among yours. A word that is only in an objective’s title still brings your key results under that objective.
- The Actions menu’s first row reads Objectives report here: the document is built from objectives, so it covers the objectives your listed key results sit under (with their teammates’ key results). The export dialog says so, shows a Role line while the Owner or Collaborator chip is on, and the report says it on its cover.
What is deliberately not here: a key result somebody archived; your teammates’ key results; and an objective you own with none of your own key results beneath it, which stays on Objectives. The phone page shows tasks only, so it has no such view. How you leave it — the tab, grouping, layout, role and order — is remembered with the rest of the board.
Pinning the header so the objectives scroll under it
Customize › Layout › Keep the header in view while scrolling keeps the whole header block — the view row and the Focus strip, with the figures, the filters and the tools — fixed at the top of the window while you scroll through the objectives underneath it. Switch it off to unpin (press it again to unpin). Useful for a long list, where you want the filters and counts to stay in view while you change the area or quarter. The pin is saved with your account, so the page opens the way you left it on any computer, and it works the same in both layouts.
Customize: every way to arrange the page, in one panel
The Customize button (the sliders icon, or the v key) opens a panel on the right. Its sections come in the same order on every page; this one has five. Each option shows how long it is kept. The general guide, with the tags and Reset, is in Customize: every view option in one panel.
- Layout — Show objectives as Kanban or List, Keep the header in view while scrolling, and Show Board at a glance (the strip’s fold).
- Show and hide — Hide finished objectives.
- Organize — Group objectives by Area or Status, Sort objectives by Grouped order, Least complete first or Most complete first; on My key results, Group key results by and Sort key results by.
- Display — Theme and app font… and All settings…, which open My settings.
- Defaults — how the board opens in a new session: Open in columns (Kanban), Group by area when a session starts, Open objectives with their key results showing and Objectives per column before “View all” (3 to 20). These are the same four settings as OKR Settings → Your defaults.
The grouping, layout, sort and Hide finished choices are tagged This session: they survive a reload and are gone when you sign out. The pin, Show Board at a glance and the Defaults are tagged Saved: they follow your account. The panel also has Reset section at the foot of each section, and Reset everything on this page… at the foot of the panel; both offer Undo. This page has no Utilities side panel.
Two layouts: List and Kanban
The List | Kanban icons in the view row (or Customize › Layout › Show objectives as) choose how the objectives are drawn. Both show exactly the same objectives — every filter, the search box and the sort apply identically. Only the presentation changes, and switching is instant because nothing is re-read.
| Layout | What it is for |
|---|---|
| List | Reading the detail. Each portfolio area is a full-width band and each objective a full-width line with its area, owner, quarter, key-result count, percentage and a progress bar — and opening one gives its key results the whole page. This is the default. |
| Kanban | Scanning the portfolio. Each area becomes a card, with the area's own health above its objectives, and the cards sit side by side so you can compare several areas at once. |
In Kanban each card carries a progress bar, with its percentage right beside it on the same line. The objective gets the whole width of the card — up to four lines — and everything about its status sits on one line under the bar, read left to right: the status pill, how far ahead or behind its pace is, how many key results are behind, whether its quarter was pushed, its check-ins and how many key results it has, with the owner's initials at the end. The status is always written out, never left to color alone. In List there is no bar on the objective row — the row already carries a status dot, a status pill and the percentage, and every key result underneath draws a bar of its own, so a fourth marker spanning the full width made a list of twenty read as a wall. Open an objective and its measures show their bars. Which one you choose is remembered — for you, on any computer. It is your preference, not the team's: choosing Kanban does not change what anyone else sees, and changing team, quarter, filters, the search or the sort never changes it back. List and Kanban were called Row and Column until August 2026 — only the names changed, so the old Row/Column names still work and nothing needs resetting.
Kanban: reading an area card
Each area is a card: its name and how much is in flight, its health as counts (2 behind · 1 slightly behind · 1 on track — press a count to filter the board to it, press again to clear), a thin bar showing the shape of the area, then its objectives as compact cards — so you can tell which area is in trouble without reading a single objective. Objectives with no area of their own gather under Unassigned.
The areas share the page. Columns grow to fill the window rather than sitting at a fixed size; once a column would get too narrow, the next area starts a new row. A wide column adds the List view's line under the title — area · owner · quarter, with the owner named in place of the initials; wider still and each card adds what its measures actually say (“2 behind · 1 on track”) at the end of its status line, the one thing the List row has no room for. Nothing is lost; it is all there in the objective when you open it.
Data Platform 4
Customer Experience 3
Unassigned 1
Click an objective card to open it in a dialog — large, sized to your window, with its key results and all their controls: check in, edit, linked work, comments, details. It is the same objective the List layout draws, in the same kind of dialog the task editors use. Click the card again, press Close, or press Escape to put it away; one objective is open at a time, and editing a key result opens on top of it without losing your place. The dialog is as tall as the objective needs and no taller; once it would run past the bottom of your window it stops there and the content scrolls inside it, with the title, area, owner, quarter and percentage pinned at the top.
A large area shows its first few objectives and offers View all N objectives. How many is yours to set: open Settings › Your defaults and change Kanban items per column — any whole number from 3 to 20, starting at 4, and remembered for good like the rest of Your defaults. Which layout you are currently in is different and lasts only the session. The number you set is the number you get: an area holding more offers View all N objectives, which never changes your setting, and Show the first N puts it back. While a search or a filter is active nothing is compacted — a match is never hidden behind View all.
Click an area name to fold it into a narrow strip — the name turns on its side, the count stays, and the width goes to the areas beside it, the same way a folded swim lane works on the team board. Click the strip to open it again. Folding is remembered for as long as you are signed in, and no longer.
Finding things
The controls along the top all narrow the same list, and they combine:
- The Organize link says how the list is grouped, and opens Customize at Organize to change it: Area or Status.
- The area, owner and quarter fields filter it, and all three let you tick more than one — ticking nothing is the same as ticking everything: All areas or Any owner.
- Owner → Unassigned is how you find work nobody has picked up. It matches an objective whose owner is empty or which has any key result with no owner.
- Owner → Former members finds work still owned by somebody who has left — see When an owner leaves.
- Area → Unassigned finds objectives that have no area. It is offered only when something in view has none, and pressing a cell in the Overview's Unassigned row opens exactly those objectives. A key result always counts under its objective's area, even when it sits in a different quarter.
- Select all and Deselect all sit above the list in both the Area and Owner fields. On Owner, a search box above the rows lets you type a name instead of scrolling — Area does not offer one, because no team has enough areas to need it. Typing only hides rows that do not match; it never changes what is ticked, and the two buttons relabel themselves Select all shown and Deselect all shown while narrowed.
- Customize › Organize › Sort objectives by orders objectives by how complete they are — least first or most first, within each group. An objective with no key results has no percentage, so it sorts last either way.
- The six health figures in the strip are buttons — press Behind to see only those, press it again, or press In view, to clear.
- Search matches objective titles, descriptions, key results, areas and owner names. Press Escape to clear it.
- Clear filters appears whenever a filter is active.
The figures always count the whole area-and-search selection, not the slice you have drilled into — so you can always see what you are filtering out, and get back. Hover a figure and its name also gives the number of key results those objectives carry, such as 34 key results, counted in the quarters you have selected — never an earlier or later quarter, and never an archived one. The figure's status is still the objective's; the Objectives list shows each key result's own.
When an owner leaves
When a team admin removes somebody from your team, or their account is deactivated, the objectives and key results they own keep them as owner. Nothing is reassigned or cleared for you, and if they come back their work is still theirs. (Somebody who leaves or is removed from the organization is different: their objectives and key results there become Unassigned straight away, and Owner → Unassigned finds them.)
- Wherever an owner is shown, they read as Former member, or as their name followed by (former member) when you can still see their name.
- A line above the Objectives list, and on the Overview, says how many objectives and key results are owned by former members. Show them narrows the board to the work they own (the same as ticking Owner → Former members). The line counts only work you could reassign, so a private goal you cannot change is not counted in it, although the Former members choice in the Owner filter still includes it.
- To give one a new owner, open it and choose somebody in Owner. Former members are not offered there. A team admin also sees Change owners in bulk on that line. It lists only the work a former member owns, says which key result belongs to whom, and changes only that work: an objective or key result a current member owns is left alone.
The page remembers how you left it
Two different things, kept apart on purpose. How you like to read boards (your defaults) is remembered for good; how the board is arranged right now — the tab, the quarter, filters and what is open — is remembered only for the session. OKRs always opens on the Overview showing the current quarter.
| Decides how the page OPENS | Lasts until you sign out |
|---|---|
| Your settings in Settings › Your defaults: Open in Kanban, Group by area, Expand objectives automatically and Kanban items per column. Saved with your account, so they work on any computer. Plus which team you were last in. | Everything you then do to the board: the tab, List or Kanban, the grouping, the sort, the area, owner, quarter and status filters, which groups you folded, which objectives you expanded — including with Expand objectives and Collapse objectives — and which key results you opened. |
A fresh session opens with every band and area expanded and every objective closed — all of the work in view, none of the detail. Tick Expand objectives automatically in Your defaults if you would rather see the key results straight away; once you have folded or unfolded anything yourself, what you did stands for the rest of the session. Refresh the page, or go to Tasks and come back, and the board is exactly as you left it. Sign out and back in, or come in tomorrow, and it opens at your defaults again — a filtered, half-expanded review from yesterday is not waiting for you.
Which team you were last looking at is remembered for good — that is which board you work on, not how you had it arranged — checked against your current membership each time, so a team you have left is never restored.
There are two pairs of these, and each one says what it acts on. Expand areas and Collapse areas, at the top of the list, fold the groups — the bands in List, the cards in Kanban, renaming itself Expand bands when you are grouped By status. Expand objectives and Collapse objectives, next to them, open the key results underneath every objective in view — a List-only control, since in Kanban the key results live in the objective's own dialog. Both act on what is currently in view, so an objective a filter has excluded is left alone. A group folded in one layout is folded in the other; which objective's dialog you had open in Kanban is not remembered at all, not even for the session.
Signing out clears all of this deliberately, so the next person to sign in on that computer does not inherit how you had the board set up. The search box is deliberately not remembered — coming back to a filtered list with no memory of why it was filtered is worse than starting clean. If a quarter you were viewing is deleted, or an objective you had open is archived, the page falls back to something real rather than showing you an empty screen.
Exporting the board, or printing it
The Actions button in the view row — just before Customize — opens a short menu: a Reports section with the two reports, a Utilities section with the CSV export, and OKR Settings under Page settings. Choose Current View and it builds a plain, printable report and hands it to your browser’s print dialog, where Save as PDF is the usual destination. It is meant for a quarterly review, a leadership update or a board pack: something you can give to somebody who does not open the application. (The Reports section’s other choice, By Member, is a different document about one person’s own work — see below.)
It exports what is on the page, and says so
The report is of the board you are looking at, not of everything the team has. Every filter that was standing when you pressed the button is honoured — the quarter, the area, the owner, the contributors, Your role, the health drill-down, the search box and Hide completed. The dialog counts the objectives for you before it builds anything, so you can see whether you meant to narrow it that far.
And the front page of the report says what was left out. Each narrowing is printed as a labeled line — Period, Area, Owner, Health, Search, Scope, Completed work — so the person you hand it to can check “was this only their own objectives?” without asking you. An export that quietly dropped half a board would be worse than no export at all, because nothing about it would look wrong.
What is in the document
A cover with the team’s name, the period and the counts; then the digest if you asked for one; then At a glance, Health and By area; then the work, by area and quarter — every objective with its progress and health, and its key results underneath. Two tick boxes shorten it: turn off Include each objective’s key results for a summary, or Include the health and by-area breakdowns to go straight from the cover to the detail.
The digest is written by your assistant; the numbers are not
Every figure in the document is computed by the application from your team’s own check-ins. The report says so in its footer. If you ask for an executive digest, an AI assistant writes the prose over figures that were worked out before it was asked — it is handed those numbers and told it may not calculate one of its own, and every figure it is allowed to mention is printed on the page underneath the paragraph. It is given no names: the facts that go to the assistant carry objective titles and numbers and no person at all.
The digest is not saved to the board, so writing one over a filtered export cannot overwrite the quarter digest the Overview keeps. Where your export is not narrowed, the digest the Overview has already written describes exactly this population, so it is offered as it stands, with its own timestamp, and nothing is sent anywhere.
The report is complete without an assistant
With no AI key set up the digest section is simply not there — not there and grayed out, not there and failing. What remains is the whole report: the scope, the figures, the health table, the area table and the full detail. The narrative was the garnish; the numbers were always the document.
Export these OKRs as a spreadsheet
Choose Export these OKRs (CSV) in Actions and the board you are looking at downloads as a .csv file that opens in Excel or Google Sheets. It is the quickest way to take one quarter, or one area, out of the application. It writes exactly what the board shows: the quarters picked in Period, and every area, owner, health, search and other filter standing when you press it. The row under the name counts what will be written, for example 62 objectives · 246 key results.
The file has one row per key result, with its objective’s title, description, area, owner and quarter repeated on each row, so you can filter and pivot it. An objective with no key result in view is one row with the key-result columns left blank. The columns are the ones in the template the importer offers, so a file you change can be imported again. Check-ins are not in it.
In My key results the file holds your own key results (the ones listed) and the objectives they sit under. The file name carries the team, the quarter and today’s date, so exports from different quarters do not overwrite one another. When nothing is in view the row is grayed out and says so; change a filter first.
One person’s report card
Press Actions and choose By Member under Reports, for a document about one person’s own work over whatever period you choose, rather than about the board as a whole.
Choosing who, and what period
Picking By Member opens a small dialog. Type a name or an email address to find someone — the list is everyone on the team you currently have open, the same team the board itself is showing.
For the period, four buttons cover the usual choices — This quarter, This year, Last 4 quarters and Custom — and a small grid lets you tick individual quarters directly: years run down the side, newest first, and the four quarters of each year run across. A quarter nobody has started yet is shown but cannot be picked; typing a date, or ticking a quarter by hand, switches the period to Custom automatically so what is selected and what the buttons say can never disagree. The dialog also tells you roughly how much the range covers before you run it, so you can see you have not picked something far narrower — or wider — than you meant to.
You can only run your own — unless you administer the team
An ordinary team member can only build a report about themselves. The person field simply will not let you choose anyone else. If you administer the team, you can build one for anyone on it. This is checked again, in full, every single time a report is opened — including if someone sends you a link straight to one — so it is never something a locked field is merely hinting at.
What the report contains
The report opens as a page of its own, not a download, so you can read it, refresh it, or come back to it before deciding whether to keep it. It has two parts:
- Objectives this person owns. Every one of them for the period you picked, with the key results from that period underneath — even a key result somebody else on the team happens to hold, because the person you asked about is accountable for the objective, not only their own piece of it. Measures from other quarters are shown as context and count toward nothing.
- Key results this person owns on somebody else’s objective. Grouped under that objective’s title, with its owner, area, team and period shown for context. This is why you may sometimes see an objective on the report that this person does not own at all — only their own measure under it is included, never the rest of that objective’s key results.
If they own none at all, the second part is where their whole record lives. The period you choose is exactly what you get — every quarter it touches, including one where nothing happened, is shown, and nothing on the page is qualified by whatever filters happen to be standing on the board behind it. If the person’s work spans more than one team, the report says so and labels each objective with its own team. A quarter that has already finished is described as it stood at the end of that quarter, with the date printed beside it. There is no score, grade, or ranking anywhere on the page: every average shown is a plain mean, and it always says how many things it was averaged over. Asking about somebody with no work at all in the period you chose still gives you a real page, simply empty, rather than a blank screen.
Sharing it
While a report is open, the address bar updates to point at it. You can copy that link and send it to a colleague; when they open it, the same who-can-see-whom check runs again for them, so a link only ever works for someone who was allowed to run that report themselves.
Printing it, or saving it as a PDF
Inside the report, Print or save PDF opens a printing step without leaving the report itself. It shows a preview of exactly what will print, alongside a short set of choices, before anything reaches your printer.
Neither button generates a file by itself. Both Save as PDF and Print simply open your browser’s own print dialog — they differ only in which destination is already chosen for you when it opens. This application does not create the PDF; your browser does. Whichever one you press, you stay on this step afterwards rather than being sent anywhere else.
Choose Letter or A4 before printing; the preview reflows to match. The three tick boxes shorten the document the same way they do for the board export — turn off Key result tables for a summary of just the objectives, or Area breakdown to leave it out entirely. Page break per quarter, off by default, starts a fresh page for every quarter shown rather than letting them run together.
Every printed page repeats the person’s name and the period at the top and a timestamp at the bottom. The health label on each measure prints as an outlined box with its own word in it, never as a color alone — so it still reads correctly if you print in black and white. And whatever you folded closed or left open while reading the report on screen makes no difference to what prints: every key result under an objective is on the page, open or not.
Two things you will not find here, on purpose
The preview is one continuous sheet with no page-by-page navigation and no page count shown — only once it actually prints does the document carry real page numbers. And a section that runs onto a second page does not repeat its heading marked “(continued)”. Both were left out deliberately: neither this application nor your browser can know how many pages a document will run to, or which page you are looking at, until printing actually happens.
OKR Settings
OKR Settings is the last row of the Actions menu in the view row, below the two reports. (It used to be in the menu under your initials; it is not there now.) There is also a link from Team Settings → OKRs → OKR access, for when you are already deciding who may use OKRs and want the areas and quarters next; it takes you to the OKRs page itself and opens settings on Areas — it does not open a second window inside the one you are in. It only appears for a team admin once OKRs are switched on.
Four tabs — Areas, Quarters, Your defaults, Bulk changes. Bulk changes is shown to anybody who has something to do in it, and each row in it carries its own gate rather than the tab gating all of them: Import from CSV… is for everybody, the bulk owner change is a team admin's, and running the import is a Super Team Admin's — see Importing a quarter from a spreadsheet.
4 objectives in this quarter RetireDelete
3 objectives in this quarter RetireDelete
Areas
Areas are what By area groups objectives by, and what the area dropdown filters on — so until you add some, everything sits under Unassigned.
The pane opens on its own heading, Portfolio areas, with a short explanation underneath. Below that is a smaller heading, Areas, over the list itself — and beneath THAT heading, before the rows, is the row that adds a new one: type a name and press Add.
Each row shows how many objectives are filed under it this quarter. Deleting an area does not delete its objectives — they simply become Unassigned, and the app tells you how many before you confirm.
Areas are shared by the whole team, so only a team admin can change them. Everyone else sees the list without the controls.
Quarters
Every objective lives in one quarter. The current one is created for you the first time somebody opens the page; add the next one here before planning starts. Open jumps the page to that quarter.
The tab you press to get here still says Quarters — only the heading inside the pane changed. Once you are in it, the pane's own heading now reads Portfolio time periods, matching Portfolio areas beside it, with the row that adds a new quarter (or a whole year at once) above the quarters themselves, the same layout as the Areas pane. Also team-admin only, for the same reason.
Your defaults
OKRs always opens on the Overview showing the current quarter. Within a session the tab, quarter and filters you choose stay put across reloads, and they are forgotten when the session closes. Your defaults below are how the board is read, for you, on any computer. None of it changes what anyone else sees.
- Group by area — group by portfolio area instead of by health.
- Expand objectives automatically — an objective you open on the board shows its key results straight away, rather than folded.
The health bands are on this tab too, under Health signal, with the sliders in it.
The board comes back the way you left it
However you arrange a board is how you will find it next time — next week as much as ten minutes later. That covers the tab you were on, List or Kanban, the grouping, the sort, the area, owner, quarter and status filters, Hide completed, Your role, Collaborators, which groups you had folded away and which objectives and measures you had open.
It is remembered per team: how you read one team's board says nothing about another's, whose areas and quarters are different anyway. Your defaults above are what a board opens with when you have not arranged it yet.
Two things are deliberately not remembered. The search box — a search is a question you are asking now, and coming back to a filtered list with no memory of why is worse than starting clean. And which objective's panel was open, because signing in should put you on the board rather than back inside one row.
Nothing needs saving; it is stored as you go, and only once you actually change something. Simply opening a board changes nothing.
Handing an objective to somebody without OKR access
The owner list offers everybody on the team, including people who have not been given OKR access. Pick one of them and the box says so before you save. If you are a team admin, saving grants them access — it is access to every objective and key result on the team; there is no per-objective version of it. If you are not a team admin you can still hand it over, but you cannot grant access, so the note tells you what will actually happen: they will not be able to open it until an admin adds them from Team settings → OKRs. The assignment is never blocked either way. Nothing is said for somebody you have invited who has not signed up yet — they get access with everything else when they claim the invitation.
The new owner is told, twice
Change the owner of an objective or a key result and the person taking it on gets an email and a notice in Messages, the same pair a task assignment sends. It is sent only when the owner actually changes and only after the change has been saved, so nobody is told about a change the database refused. The notice is posted by the system, on behalf of whoever made the change; nobody can delete it, including the person who made the change. An invited person who has not signed up yet is not emailed or notified — there is no account to reach. They get both the moment they claim their invitation.
A new owner gets the owner email instead of the update.
Bulk changes: moving several objectives to a new owner
Reassigning five or ten objectives one at a time is the job this replaces. Open OKR Settings → Bulk changes → Choose objectives…, tick the ones you are moving, pick the person, and press Change owner. It acts on the objectives currently in view, so narrow the board first if you want a shorter list to work from. Also change the owner of their key results moves the measures with the objective, offered rather than assumed, since an objective can be owned by a lead whose individual measures belong to other people.
You are told exactly what it will do before it runs — “Change the owner of 6 objectives and 12 key results to Daniel Cole?” — and what happened afterwards, as counts: 4 changed · 1 refused · 1 failed. Refused is not failed: it means somebody edited that objective while this was running, so it was left alone rather than overwritten. Nothing else about an objective changes. Only a team admin sees this tab — anyone on the team can still change an owner one objective at a time from the board.
Three kinds of settings: My settings, Team Settings and OKR Settings
OKR Settings is this board's own — areas, quarters, your defaults, bulk changes. It is not the only settings page with the word in it; three deliberately different scopes, listed widest first. My settings and Team Settings are in the menu under your initials; OKR Settings is in Actions:
- My settings — yours. The theme, the application font, your default team, email and your AI assistant. The same pane on every page of the suite.
- Team Settings — your team's, if you administer one. It opens Team settings on its Team tab.
- OKR Settings — this board's.
It is My settings on all five pages of the suite, and the possessive is the point: it is the one that belongs to you.
All three open over the board, in place. The objectives stay where they are behind the pane; close it and you are still exactly where you were, with the same filters, the same quarter and the same objectives open. Profile & account, at the top of the menu under your initials, also opens over the board.
Two doors into Team settings, and they open on different tabs
Team Settings here opens the dialog on its Team tab. On the team board, Actions → Board settings… opens the same dialog on the Boards tab instead, with the board you were reading already picked out. Both are the whole dialog and every tab is reachable from either. See the fuller explanation in Team help for the second name it grows into once your Organization is named.
Updating a key result
The progress bar is the control. Drag it, or type the number in the box beside it, and it saves — there is no Edit dialog to go through to move a measure. It works from the keyboard too: focus the bar and use the arrow keys, or Home and End for the ends. Hold Shift for larger steps.
Measures you hold inside a range
Not every key result is a journey to 100%. "Hold sprint health at or above B" or "keep p95 latency under 200ms" is Control — stay inside a band: choose that Direction and the form asks for an At least and/or an At most instead of a start and a target, because a band has no journey to be part-way along.
These are described in their own words throughout. The row says inside the band or outside the band rather than "34 days ahead", the detail panel shows the floor, the ceiling and whether it is holding, and the check-in dialog states the band instead of a target. A measure whose goal is a score of 85 is never described as a percentage of 100.
If you have chosen Control but set neither bound, everything says no band set — nothing is being checked until you give it an edge.
What is being measured
A key result carries more than two numbers. In Edit you can say:
| Field | What it is for |
|---|---|
| What is counted | “# of signups”, “% onboarded”. The title says what the goal is; this says what the number on the axis is. |
| Direction | Increase (higher is better), Decrease (lower is better), or Control (stay inside a band). |
| At least / At most | The band for a control measure. One or both. |
A control measure is not a journey — “hold attrition between 4% and 8%” has nowhere to travel to. So it gets a plain verdict, Inside the band or Outside the band, rather than a progress bar, and it counts as met while it holds. Without this it would sit at 0% and drag every roll-up above it down.
Who is on it: owner and contributors
Objectives and key results both name people the same way, and the field is in the same place in both editors — beside Owner.
Every key result has one owner — the person who answers for the number — and every objective has one too. In Edit you can also name collaborators: everybody else working on it. Press the gray person circle next to Collaborators and the same picker opens that you use to share a note — search by name or email, tick as many people as you want, then press Done (Cancel changes nothing).
They show on the key result itself, right after the owner, as Collaborators: Ashley Davis, James Reed. Beyond two it names the first two and counts the rest, and hovering shows all of them. If nobody else is on the measure, nothing about contributors appears at all — just the owner. Collaborators are a record of who is involved — they do not change who can edit the key result or the objective; anyone on the team with OKRs switched on can already do that. The one exception is a private objective, where collaborators are also the people who can see it.
On an objective it works identically. Open Edit, press the gray person circle next to Collaborators, tick people, press Done. The objective card then shows them the same way a key result does — two names, then +N collaborators.
The detail behind a key result, folded away
Details and Linked work stay lit while their panel is open, so you can see at a glance what you have already opened. The panel is headed Details to match the button. Every other button on the row — Check in, Edit, Comments, Copy link — works whether a panel is open or not.
Copy link copies a link straight to this key result — the same control as an objective's own Copy link, one row down.
Press Details on a key result and it opens a workspace under the row, in five sections you can fold independently: Measurement (the baseline, current and target, progress against the quarter clock), Metric (what is counted, direction, unit, dates, owner and contributors), Check-ins, Supporting tasks and Insight.
A folded section still tells you what is in it. Measurement collapses to something like 62% of target · 3 days behind, Supporting tasks to 4 supporting tasks. You can read the whole measure with everything shut. Sections that hold something open on their own and empty ones start folded (Measurement always opens). A section you open or fold stays that way until you close the panel; nothing about folding is remembered against your account.
Health is worked out, never set
There is no health field to change. It is computed from the numbers and the calendar every time the page draws — move a measure and its health, its objective's health and every roll-up above it follow immediately. A health you could set by hand would be right on the day somebody set it and quietly wrong afterwards.
Supporting tasks (Linked work) — you see your own
Linked work on a key result shows your tasks pointing at it — title, who it is for, when it is due — and pressing one opens that task’s own editor over the page, so you stay on the measure. Link a task attaches one you already have; + Add task creates a new one and links it in a single step, returning you to the measure with it showing underneath.
A key result is a team measure, so several people usually link their own work to it. This panel is your view of it: it lists tasks you own, and tasks that name you as owner or assignee. Other people's linked tasks are not shown here, and the “3 linked tasks” count beside the measure counts the same ones, so the number always matches the list. If none of your tasks are linked yet it says so — that does not mean nobody is working on the measure. A task created this way is one of your own tasks; who can see it is decided exactly as it is for any other task of yours. The “3 linked tasks” count is also the way in — press it and the panel opens, the same as pressing Linked work. A task in that list opens the real task in its own editor — the same one Tasks or the team board would show you — framed over OKRs: nothing about it is a copy made for the key result. Close it and the list shows what you changed; Open in Tasks or Open on the board at the top of that window takes you to the full page instead. (A middle-click or Ctrl/⌘-click still opens it in a new tab.)
Writing insights for everything at once
In the Focus strip’s tools, Re-evaluate OKRs in view (the light bulb, labeled Re-evaluate on a wide screen) writes an insight for every objective and key result currently shown — useful at the start of a quarter or after a round of check-ins, when doing them one at a time would be dozens of clicks.
The whole board goes in one request, and it tells you what it will cost before it starts, naming both the number of items and how much it is about to send. Anything whose figures have not changed since its insight was written is skipped and never reaches the request. A very large board needs more than one request, and it says so before it starts — past roughly 145 items the work is split, and the count is named in the confirmation. Nothing is saved until the reply comes back — closing the tab halfway through loses the whole run. But a reply that only covers part of the board still writes every answer it contains: whatever it could not cover is counted and reported, with a line like 253 evaluated · 249 written · 4 failed, and a Retry failed button that re-runs only those. Only the latest insight is kept for each objective and key result — rewriting one replaces it; there is no history to sift through.
Other people editing at the same time
OKRs are a team's, so several people work on them at once. While live editing is on, other people's changes arrive on their own — you will see a short Updated note when they do. They wait while you have a dialog open or are dragging a progress bar. Otherwise they appear when you come back to the tab or press Refresh; nothing refreshes on a timer.
If somebody saves a change to the same objective or key result while you have it open, your save is refused rather than silently overwriting theirs. The editor stays open with everything you typed still in it, and tells you what happened so you can check their version and reapply anything still needed. Dragging a progress bar behaves the same way: their number is shown, and you can set yours again if it is still right.
Filtering by quarter, and what the percentages mean
The control captioned Period opens a grid of quarters, two years at a time. Click a quarter to light it and click it again to put it out; click one and then Shift-click another to take the whole run between them. Four quick picks sit above the grid — Current quarter, Year to date, Last 4 quarters and All — and each of those replaces your selection rather than adding to it.
Nothing changes on the board until you press Apply. Esc, or a click outside, closes the panel and discards whatever you had staged. Use Earlier years and Later years to move the two-year window; a quarter you picked and then paged out of sight stays picked.
The number on each quarter is how many objectives are filed in that quarter — all of them, whatever your filters are set to. So a quarter can show 3 and still look empty when you open it: your filters are hiding them, and the board says so: it names how many were hidden and lists every filter that is on. Current quarter, beside the control, takes you straight back to the quarter today falls in. It grays out when that is already all you are looking at, or when no quarter covers today.
When a filter is on, an objective's percentage covers only the measures in view. If some of its key results are in other quarters you will see a +N outside flag next to the percentage — in List and in Kanban alike — and hovering it says how many and which quarters they are in; on a Kanban card the flag carries it on its own, because a sentence per card would be a wall of text. Press the flag to see which key results those are. A small list opens beside it, grouped by quarter with the earliest first, and each line names the key result, whose it is and how far along it is. It opens from the keyboard too: Tab to the flag and press Enter or Space; Esc closes it. A measure that has been archived is still listed, labeled archived. To bring any of them into the board and into the percentage, widen Period.
Moving the progress bar
Drag the bar on a key result, or type the number in the box beside it. Progress is always a whole percentage — while you are dragging, the bar, the number and what a screen reader announces all say the same thing, and none of them show decimals.
The bar works from the keyboard too. Tab to it, then ←/→ move one percent, Shift with them moves ten, Home is 0% and End is 100%.
The value saves when you let go, not on every pixel, and a check-in box then offers itself. Dismissing it keeps the new value — it only skips writing a note.
Adding a whole year of quarters
In Settings → Cycles, Add whole year creates Q1 to Q4 with the right dates in one press. Quarters you already have are left alone, so adding a year you started early fills in the rest rather than complaining.
Written insights
A key result, an objective and the quarter digest can each carry a short written reading of their figures. Press Write insight (or Regenerate) and one is produced from the numbers already on the page.
The assistant is never asked what the numbers are
Progress, pace, health, counts and dates are all worked out by the application and handed over. The assistant explains them; it cannot calculate or invent one. That is why the figures always sit beside the words that describe them.
It uses whichever assistant you configured in Tasks' settings. With none configured, an insight already written stays readable and the regenerate button is simply not offered. Each insight says when it was written and who wrote it — “Written Aug 27, 2026 at 5:15 PM EDT · generated by your personal AI assistant”, in the zone your clock is set to in Tasks. No provider is named. When the underlying numbers move, the insight says “the figures have changed since this was written” rather than quietly reading as current. Nothing regenerates on its own; if a regeneration fails, the previous one stays exactly where it was.
What an area means
An area is simply a label an objective sits under. Your team chooses what areas mean to it — departments, products, functions, or anything else.
Retire rather than delete. An area with objectives under it cannot be removed without orphaning them, so retiring stops it being offered on new objectives while everything already filed under it keeps it. Restore brings it back.
Only a team administrator can change any of this. Which sections you fold and how you have arranged the page are yours alone.
The review panels: carryover, hygiene and the digest
Underneath the quarter grid on Overview are three panels that answer a different question from the rest of the page. The grid says where things stand; these say what needs a decision this week.
Carryover
Key results still open in a quarter that has already ended. Nobody chose to carry them — they were simply never closed — and left alone they pile up until the OKR set stops describing anything real.
The list is ordered by how long each has been sitting, longest first, because that is the ordering that tells you where to start. Completed and archived measures never appear here: they finished.
Click a row and its editor opens right there, over the Overview — finish it, move it to this quarter, or archive it, press Save, and it drops off the list. You stay where you were, so a list of ten is ten decisions rather than twenty trips to another screen. The › at the end of the row is the other way: it takes you to the measure in the objectives list, among its siblings and its check-in history.
“That record is in a quarter this board is not showing”
Carryover looks across every quarter, while the board itself is showing whichever quarters the Period control names. When a carried-over measure belongs to a quarter you are not currently showing, the editor cannot open over it and you are taken to the objectives list instead, with a note saying why. Choose All quarters in Period and the row opens its editor directly.
Data hygiene
Records nobody can act on. Each row is a finding, not a statistic — click it and you get the list of exactly which objectives or key results it means. Click one of those and its editor opens, the same way a carryover row works: an objective’s finding opens the objective, a key result’s opens the key result, and the › beside it goes to the objectives list instead.
A key result's row carries one more control beside that chevron — a small circular button that opens the objective it belongs to, so you do not have to close the measure's editor and go looking for it separately just to see whether the objective around it needs updating too. An objective-level finding (nothing measurable, no owner) does not need this: clicking the row already opens the objective. An objective’s editor has an Add key result button at the top of the window, beside the ✕: it opens the new-key-result form for that objective, saving first if you changed anything. A key result’s editor and its Check in window have Open in objective in the same place: it closes the window and takes you to the Objectives view with that objective open and the key result highlighted. If you are already looking at that objective it simply scrolls back to it without changing anything; if a filter was hiding it, only the filters that were hiding it (Status, Assigned to me, Updated within, Area, Owner, Search and so on) are cleared, and a message says which. If you changed the key result’s form, Open in objective saves it first (and stays put showing the error if it cannot); in Check in it asks you to record or cancel a typed check-in first. Every row in the list also shows who owns it (the key result’s owner, or the objective’s for an objective), so you can see who to chase without opening each one. Export CSV, at the top of the list beside the ✕, downloads the list you are looking at as a spreadsheet — one row per objective or key result, with the owner’s name and email first, so you can pivot it by person to see who needs to update what (for example, to email everyone with a key result that has not moved). It also carries the objective, area, quarter, team, the measure’s current, start and target values, and a link that opens each item; it holds only what the list shows you, and a key result with no owner reads Unassigned. It does not include check-in dates.
| Finding | Why it matters |
|---|---|
| Objectives with nothing measurable | Cannot be tracked, reported on, or known to be finished. |
| Objectives with no owner | Nobody has been asked. An unowned outcome is an intention, not a commitment. |
| Key results with no movement | Still sitting at their starting value, in a quarter already under way. A quarter that has not started yet, or one that has already ended, is never counted here — a stalled measure in a closed quarter is Overdue's or Finished but never closed's finding to raise, not this one's. A key result whose value has moved in either direction since it started is not counted here, even if it moved the wrong way: that one reads Behind in its status instead. |
| Overdue in a quarter that has ended | The quarter closed with this still open. It needs finishing, moving or closing. A due date inside the quarter still under way is not raised here. |
| Finished but never closed | At target in a quarter that has ended, still shown as active — so every roll-up above reads worse than the truth. |
| Pace disagrees with state | Marked complete but short of target, or well behind with nothing said. |
| Dated outside its quarter | The pace it is being judged against is not its own. |
Digest
A summary you can paste into an email or a chat channel. The figures are always there — objectives, key results, average progress, completed key results, carryover — and Copy text takes them whether or not you use AI. It copies exactly that: text, laid out to paste straight into a message without reformatting. There is no chart here to copy; the ring drawings live in the quarter grid further up the page.
It describes whatever the Period control says. Pick one quarter and the digest is about that quarter, and tells you how much of it has gone. Pick All quarters — or several — and it widens to cover them all, and the Quarter elapsed figure steps aside, because there is no single quarter for it to be a share of.
If you have an AI assistant configured in Tasks' settings, Write digest adds a short narrative underneath. It reads only the figures shown above it: the assistant is never asked what the numbers are, so it cannot get them wrong. It uses whichever provider you configured — nothing here is tied to one vendor.
“The numbers have moved since this was written”
A digest is a paragraph about figures that keep changing. When the underlying numbers no longer match the ones it was written from, it says so rather than quietly reading as current. Press Regenerate for a fresh one — and if that fails, the previous digest stays exactly where it was.
An objective can span several quarters
A key result belongs to one quarter. An objective belongs to whichever quarters its key results are measured in, so a single outcome can carry Q3 and Q4 measures and will appear in both quarters' views. Filing an objective in a quarter does not fence it there.
Connecting a task to an outcome
Open any task — in Tasks or on a team board — and tick Mark as an OKR. That checkbox is the way in: with it unticked the task is an ordinary task and none of this appears.
Ticking it opens the picker straight away, because a task cannot be marked as an OKR without supporting one. Everything you need is in that one dialog:
| In the dialog | Use it when |
|---|---|
| The search list | The outcome already exists — the usual case. Type to narrow it. |
| The quarter filter | You know roughly when the outcome belongs and the list is long. |
| Objective / key result | Switch what you are searching. Link to a key result when this work moves that measure; link to an objective when it supports the outcome without moving a particular number. |
| Create objective | The outcome does not exist yet. It is created and the task is linked to it in one step. |
| Create key result | The objective exists but the measure does not. |
Those two open the same forms you would get on the OKRs page, with the same fields — owner, collaborators, the quarter, the area, and for a key result what it measures, its unit, its direction and its start and target. They are not a shortened version: an outcome created from a task is the same kind of outcome as any other, and you do not have to go and finish it somewhere else afterwards.
Pressing Cancel on either form returns you to the list you came from rather than closing everything, so changing your mind costs one press.
Close the dialog without linking or creating anything and the checkbox turns itself back off — nothing is saved, because a task marked as OKR work that supports no outcome tells everyone reading the board something untrue.
The Supports section underneath carries Link objective and Link key result for a task that is marked but not yet connected. Both open the same dialog, so you can still create one from there.
If you belong to one team, it is used automatically. If you belong to several, you are asked which one first, and you then see only that team's objectives. A task on a team board already belongs to a team, so it never asks.
Measured and unmeasured work
Most tasks support a key result, so the work stays visible beside the number it serves. Some support an objective directly: running the quarterly customer interviews supports “understand why customers churn” without moving any single number. Linking those to the objective keeps them visible without inventing a measure nobody intends to track.
Getting to the outcome from the task
A connected task shows what it supports, how that measure is doing, and two ways through: View KR opens the key result, and Objective opens the outcome above it. Either one takes you to that exact item on the OKR page — expanded, scrolled to and highlighted — switching quarter if it belongs to a different one. You are not dropped on the OKR page to go looking for it.
Changing or removing the connection
Once a task is connected the four choices are replaced by two: Change and Remove link. Change offers the same searchable list and swaps the connection over for you — it links the new one first, so a task is never left supporting nothing.
Removing a link never deletes the objective
It removes the connection only. Objectives and key results are shared — other people's work may support the same one — so they stay exactly as they are.
Unticking “Mark as an OKR”
Nothing is unlinked. Unticking the box hides the OKR workflow for that task; the connection stays exactly where it was, and ticking the box again brings it straight back. The task tells you so rather than going quiet, because a section that simply vanishes reads as a link that was deleted.
Removing a connection is its own deliberate action — the Remove link button — and it never touches the objective or key result either. Once a task's last link is removed it supports nothing, so Mark as an OKR turns itself off and the OKR badge leaves the card.
What linking does not change
Connecting a task to an outcome adds context and nothing else. It does not change who can see the task, who it is assigned to, or whether it is on a board. A private task linked to a team objective is still a private task — your colleagues see the objective, not your task.
You can only link to objectives in teams you belong to, and only on tasks you own.
Seeing the outcome from a task
Open any task and, under the board fields, a Supports section shows the outcome that task moves: the objective, the key result beneath it, where that number is now, and how it is tracking against the quarter. Open takes you to the OKRs page.
That is the answer to "why am I doing this?" without leaving the task. It is read-only on purpose — outcomes are edited on the OKRs page, so the numbers have one home rather than two that can disagree.
If the task is not linked to anything, the section says so and offers a way over. If your team has not switched OKRs on, the section does not appear at all.
Who can change what
OKR access is granted person by person: a team administrator adds each person in Team settings, and a member not added cannot open OKRs. Administrators have access automatically. Everyone with access sees every objective on that team. Editing is narrower: the owner, whoever created it, anyone listed as a contributor, and team administrators. If a button is missing, that is why.
Deleting an objective deletes its key results, check-ins and comments with it, and the app asks first.
Only a team admin can switch the whole OKR feature on or off for the team, from Team settings: the first card on the OKRs tab, or the card on the Teams tab.