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.

Ideas for custom fields

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

  • 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
  • Priorities
    A list with the most important things you plan to do to achieve your objective
  • Opportunity cost
    What other activities are you sacrificing in order to do this one 

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

Types of custom fields

There are several types of custom fields you can add:

  • Text field - a single line of text appropriate for short text entries
  • Text area - a multi-line text field appropriate for longer text entries
  • Checkbox - a simple checkbox appropriate for true or false values 
  • Drop-down menu - a single option drop-down menu appropriate for a one-choice option (e.g. States)
  • Multi-select list - a multiple option list appropriate for multiple options choice
  • One option list - a single option list, similar to the drop-down menu but more appropriate when there're a few choices (e.g. gender)
  • Date picker - a single date value appropriate for selecting dates such as deadlines
  • Assignee selector - a selector of how many assignees and types of assignees that can be selected per Objective or Key Result

How to add custom fields

In order to define custom fields and add them to the OKRs, you should have permissions for managing the configuration of Gtmhub. 

  1. Log in to Gtmhub
  2. Navigate to Setup (the gear in the top right corner) > Configuration
  3. From the menu, select Custom fields
  4. Click on the Add new custom field box
  5. Fill in the form as follows
  • 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 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 fields

You can use custom fields the same way you use other fields. If you have defined the field risks, discussed above, this is how it would look like.

Did this answer your question?