Gtmhub allows you to define custom fields that go with every OKR. By default, Gtmhub will store Name, Description, Owner and Parent OKR for each OKR. However, you can easily add more fields.

Ideas for custom fields

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

  • Risks
    Define risks which you may face while executing on your objective
  • Execution notes
    Simple notes which explain to everyone how you plan to achieve the objective
  • Priorities
    List of most important things you plan to do in order to achieve your objective
  • Opportunity cost
    What is it that you are not doing, because you are doing this
  • To-do list
    What are you going to do to achieve your key results.

Types of custom fields

You can add any number of custom fields to your OKRs. There are several types of custom fields you can add:

  • Text field - single line of text, appropriate for short text entries
  • Text area - multi-line textual field, appropriate for longer text entries
  • Checkbox - simple checkbox, appropriate for values that are either true or false
  • Drop-down menu - single option drop-down menu, appropriate for a single choice between many possible options (e.g. States)
  • Multi-select list - multiple option list, appropriate for selection multiple options for a list of choices
  • One option list - single option list, similar to drop-down menu, but more appropriate to be used when there is only few choices (e.g. gender)
  • Date picker - a single date value, appropriate for selecting dates, such as deadlines and so on
  • To-do like list - allows you to define to do lists for each objective

How to define custom fields

In order to define custom-fields you need to have permissions for managing the configuration of Gtmhub. 

  1. Log in to Gtmhub
  2. Navigate to Setup > 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
    Programatic name of the field. This field has several rules: must be unique, must be lowercase, can be only letters, 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 are no rules 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.
  • Required: Unchecked
    If this is checked, every user will must set the value of this field. To make the field optional, leave this unchecked.

Click Save button.

Using custom fields

Custom fields are used in the same way as other fields. If we have defined the field risks, described in the previous paragraph, this is how it would look like.

Did this answer your question?