Overview

When you create an Individual Goal or Team OKR, there are optional and required fields to fill in order to create context around your statement of intent. Let's take a look at the Objective Fields and the information to which they correlate. 

List of Objective Fields

Note: Fields marked with an asterisk* are required, and unmarked fields are optional. 

• Objective Name*: Give your objective a name and pick the team that owns the objective. Add a narrative that provides business or strategic context, or adds insight.
  
  
• Description: Include context behind the objective to provide additional clarity to management and the team.
  
  
• Team*: For Team Objectives only, determine which team the objective is for. It will default to the last Team you visited where you're a Manager or a Co-Manager.
  
  Note: Only Teams where you're a Manager or Co-Manager can be searched and selected. 
• Owner*: Identify who owns the Objective on the Team. If this is a Individual Goal, you can assign it to someone who reports to you directly.
  
  Note: For Team OKRs, only members of the team in WorkBoard who have manager or co-manager permissions can be set as the owner.
• Duration*: Set a time period in which you want to reach the objective. OKRs traditionally span a quarter because they’re faster, more focused, and accelerate both results and learning. You can set the time period for each objective to whatever works best for you.
  
  
• Objective Alignment: Work with your Team during your localization sessions to determine to which Objective(s) you should align your Objective. Your objective may align to one or more of your manager's OKRs or a different Team altogether.
  
  
• View Permissions in Addition to Owner*: The default shows the objective to the entire organization, which you can adjust as needed. Copy the same permissions to each key result or metric, or set individual view permissions on each key result.
  
  
• Objective Category: An organization admin enabled with Governance access will create Objective categories. They are used to categorize Objectives based on their relationship to key strategic initiatives or themes across the enterprise to see how time and effort is being prioritized, which is encouraged at the upper-levels in an organization.
  
  
• Add carryover OKRs
  • If your Objective is a carryover of another Objective, you can use the 'Objective is carry over of' field to add the historical OKR. This will populate the new Objective into the timeline view to view its progress quarter-over-quarter.
• Add dependencies or related workstreams: 
  • If your objective depends on other objectives or workstreams, add them by searching by Team, Objective name, or Objective Owner. 
    
    
  • For Workstreams, you can search by Team or Workstream name. When people align to your Objective, they're automatically added as Objective Dependencies. When you add a Workstream Key Result on an OKR, it automatically adds that Workstream to the Objective-level.