1. OKR Tracking System
  2. Features
  3. Objectives and alignment
Feature · Objectives and alignment

Objectives and alignment

Keep each objective tied to an organization, a named owner and the dates for its work.

OverviewMy Objectives
OKR Tracking System · Objectives and alignment

My Objectives

Objectives

New
Objective codeObjectiveStatusEnd dateProgress against target
OC-656OBJ-256Planned04 OctPAT-985
OC-991OBJ-167Active10 OctPAT-851
OC-127OBJ-366At risk27 OctPAT-709
OC-997OBJ-457Completed26 OctPAT-243
OC-264OBJ-283Planned16 OctPAT-383
6 of 6 records
OC-656Objectives · OBJ-25383
Planned
ObjectiveOBJ-256
End date04 Oct
Progress against targetPAT-985
Example screen with sample data

What you can do

Start with the objective and its owner

An objective carries a code, description, schedule, budget, delivery method and status. The owner can compare estimated, actual and logged hours alongside counts of work packages, tasks, blockers, risks and key results. The progress text belongs to the objective, so a review can start from the outcome the team is pursuing and move into its supporting work. An organization link keeps related objectives together.

At the review, begin with the objective record and read the linked result and delivery work in sequence. The schedule and progress text give the conversation a shared starting point. A status change should reflect the owner’s current decision, especially when a blocker or risk may affect the end date.

How the work is organized

  • Set direction. The Delivery Lead names the objective, its owner and its schedule.
  • Connect delivery. Work packages, tasks and key results give the objective its review context.
  • Update status. The lead checks blockers, risks and target dates before changing the objective state.

What to agree during setup

Agree who owns each objective, how the team uses planned, active, at-risk and completed, and when to change a target date. Decide how an organization is selected for internal objectives. Set a cadence for reading the hours, blocker and risk counts with the key result owner. Rehearse an active objective with a blocked task and a pending key result. Ask the lead whether the end date is still credible and who should change the status if it is at risk.

Check the handoff on an actual case

A delivery lead creates an objective for an organization and gives it a start and end date. The project manager then adds a work package and tasks. At the weekly review, the objective remains active while a blocker is triaged; the lead marks it at risk when the blocker threatens the end date. The key result owner has a dated checkpoint to discuss rather than a vague statement that work is underway. The lead checks that the at-risk status remains visible in Active Objectives and that the Project Manager owns the next action on the blocker. The decision stays on the objective.

What your team sees

  • Active Objectives — Objectives with current delivery status, owner, dates and progress text.
  • Objective Schedule — Planned and active work placed against start and end dates.

Follow the work through

What it keeps track of

Data model
Objectives
Engagements delivered for an organization, with budget and schedule.
Organizations
Client and internal business organizations that projects are delivered for.
Team members
Delivery staff with role, practice and weekly capacity.
Key results
Dated checkpoints a project must meet.

Who uses it

Permissions
Delivery Lead
, Project Manager.
The Delivery Lead owns objective status; the Project Manager brings task, hour and risk context to the review.

Set up OKR Tracking System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started