Create an Objective

An Objective explains what the team is trying to achieve

Create an Objective when a Session needs a clear direction. The Objective should say what should become true by the end of the planning period. It should be understandable without a meeting transcript.

An Objective is not the measurement and not the task list. Add Key Results for measurement. Add Initiatives when the Objective or Key Result needs its own connected canvas.

Availability and permissions

Where to create an Objective

Open Goals/OKRs, then open the active Session where the Objective belongs. Use the create Objective action. If you cannot find the Session, read Create a Session and Troubleshoot OKR permissions.

After creating the Objective, open its detail view to add Key Results, Initiatives, owners, dates, status, notes, or Check-ins. Use Tree view when you need to review or adjust Objective hierarchy.

Write the Objective

Use plain language. A good Objective names a meaningful direction without hiding all the work inside the title.

The better versions can support multiple Key Results. They also help reviewers understand why the work matters.

Create the Objective

1. Open the correct workspace.
2. Open Goals/OKRs.
3. Open the active Session.
4. Choose the action to create an Objective.
5. Enter a clear title.
6. Add owner, status, tags, dates, description, or other fields available in your workspace.
7. Save the Objective.
8. Add Key Results so progress can be measured.

If the row opens a detail panel instead of the menu you expected, return to the row action or menu control. In Goals/OKRs tables, row clicks, menu actions, status controls, and detail panels can have different behavior.

Add structure after the Objective

Once the Objective exists, add Key Results. A strong Objective usually has enough Key Results to measure the outcome without becoming noisy.

Then add Initiatives when the work needs a connected canvas. Initiatives open as canvases, so the team can keep plans, tasks, subtasks where available, notes, review material, and execution context connected to the Goal/OKR.

Use Check-ins throughout the Session to keep progress current. A Check-in should explain what changed and why.

Use Objective hierarchy when it clarifies strategy

Objectives can be organized hierarchically when one Objective supports another. A parent Objective represents the broader direction. A child Objective represents a more specific direction that contributes to it.

Use hierarchy for real alignment, such as company Objectives with department Objectives underneath, launch Objectives with readiness Objectives underneath, or a broad customer-experience Objective with product, support, and education Objectives underneath.

Do not create hierarchy just to store tasks. Tasks and execution details belong in the connected Initiative canvas. Key Results belong under the Objective they measure.

Where your access and current view support it, you can rearrange hierarchy by dragging Objectives in List or Tree view.

If drag-and-drop is unavailable, clear filters and search, return to the default sorting view, and confirm you have edit permission.

Examples

Objective: Make permissions understandable for workspace admins.

Key Result: Reduce access-related support conversations by 30%.

Initiative: Rewrite workspace roles, sharing, and deactivated access docs in a connected canvas.

Check-in: Workspace articles are drafted. Collaboration articles are next. Permission concepts now link back to the roles article.

This Objective works because the direction, measurement, and work are separate.

Permission and visibility notes

If you can create an Objective but someone else cannot edit it, check their Goals/OKRs permission and the Session state.

If an Objective contains Initiatives, the connected canvas has its own access requirements. Share the canvas separately if reviewers need to open it.

If the Objective belongs to an archived Session, check the Session state before assuming your role changed.

Common mistakes

Do not create an Objective for every task. Objectives should describe outcomes.

Do not make the Objective title so broad that no one can tell what changed at the end of the Session.

Do not skip Key Results. Without Key Results, the Objective becomes a statement of intent with no measurable review path.

Do not duplicate an Objective because it is filtered out. Clear filters and check the correct Session first.

Do not turn every supporting idea into a child Objective. If the item is work to do, create an Initiative instead.

Recover when Objective creation fails

If the create action is missing, check whether you are in the right workspace and active Session. Then check your Goals/OKRs edit permission.

If the Objective saves but disappears, clear filters, search by title, and confirm it was not created in another Session.

If the Objective is read-only, ask the owner or workspace admin to review your role and item access. Use Troubleshoot OKR permissions.

If you accidentally created the Objective in the wrong Session, move, recreate, or archive according to your workspace policy. Avoid leaving duplicate Objectives active in two Sessions.

If the Objective belongs under another Objective, use Tree view or the supported list drag-and-drop path to place it correctly. Confirm the hierarchy after moving so the Session still reads correctly in every view.