You can define custom fields with Gtmhub that go with every OKR. By default, Gtmhub will store info from the built-in fields Name, Description, Owner and Parent OKR for each Objective & Key Result. However, you can easily add more fields.

Check out this general guide for Custom Fields.

Ideas for custom OKR fields

If you're wondering how exactly to use custom fields, here are some ideas that some of our customers find useful.

For Objectives

  • Risks - Define risks which you may face on the way of attaining your objective
  • Execution notes - Simple notes which explain how you plan to achieve the objective
  • Strategic initiative - Key cross-company/departmental initiatives which tie to the objective
  •  Opportunity cost - What other activities are you sacrificing in order to do this one

For Key Results

  • Responsible - Identify teams or individuals that share the responsibility for a Key Result
  • Mitigation - Describe what you will do to mitigate risks while pursuing progress

For Key Result updates

  • Priorities for the week - A list with the most important things you plan to do to achieve your OKR
  • Upcoming Projects - A list of projects coming up in the next 4 weeks
  • Health - Key things you want to keep your eyes on (e.g. team health, key customer relationships, etc.)
  • Score - Evaluation of KRs at the mid-point and end of an OKR session. (Note: Andy Grove’s method of grading OKRs is a “yes” or “no” approach. You either delivered or failed to deliver. A more advanced method is to score each Key Result on a scale from "0.0 to 1.0" where “0.0 - 0.3” is a failure to make progress; “0.4-0.6” means some progress was made but, you didn’t quite make it; to “0.7-1.0” means you succeeded.) 

Note that you can add as many custom fields as you like to your OKRs. There're no limits. 

Name: risks
Programmatic name of the field. This field has several requirements: must be unique, must be lowercase, can be letters only, has to be between 4 and 12 characters

UI Label: Risks
This is the name of the field that will be displayed in the user interface. There're no requirements here

Description: What may prevent us from achieving this objective
A hint to users on how to use this field

UI Selector: Text area
Type of the field depends on the type of information you want to store in this field

Target type: Objective or Key Result

Required: Unchecked
If this is checked, every user must fill in the value of this field when creating an OKR. To make the field optional, leave this unchecked.

Click the Save button.

Using custom OKR fields

You can use custom fields the same way you use other fields. 

Objective Custom Field Example

If you have defined the field risks, discussed above, this is how it would look like.

Key Result Custom Field Example

If you have defined the field responsible—where you identify teams or individuals that share the responsibility for a Key Result—this is how it would look.

Key Result Update Custom Field Example

If you defined the field scoring—where you grade KRs mid-session or at the end  of a session—this is how it would look.

Did this answer your question?