Specify the type of the objective to organize them.

Use the objective type to define types of objectives.

Relate the objective to a theme.

Typically the objective is added to a theme as child document. In this case the reference to the theme is automatically rendered.

List other objectives this objective supports. The objectives listed here will be rendered in the Supporting Objectives section.

The start date when the persueing pursuing of this objective begins.

Typically the objective is added to a theme as child document. In this case the start date is automatically rendered.

Note that the Start property is hidden and rendered as part of the Cycle property.

The end date when this objective ended.

Typically the objective is added to a theme as child document. In this case the end date is automatically rendered.

Note that the End property is hidden and rendered as part of the Cycle property.

For brevity and to save space the start and end date are rendered with the Cycle property as a period.

Log the date the objective is planned to be solved.

The deadline allows to order objectives and provide a more fine-grained structuring within the defined cycle.

Reference a priority to related this objective's importance to other objectives.

Log the value scored by the end of the period. The format of the value is a decimal value between .01 (or .05) and 1.

In case the short description is not enough, the description section provides room for more detailed information about the objective.

Describe why this objective is useful for your business. State the problem to be solved.

You may run the 5-whys to dig deeper.

List key results to measure the level of success in accomplish the objective. The completion of all key results must result in the achievment achievement of the objective.

Check to pair key results to aim at quality and quantity to make sustainable progress.

Key results added as child documents are automatically listed.

Provide a check-in for each interval within a cycle.

Check-ins added as child documents are automatically listed.

List all objectives that support this objective.

All objectives that declare this objective as their logical parent are automatically listed.

List objectives that are related to get in touch with the owners to solve problems or discuss opportunities.

All objectives of the same type are automatically listed.

Add a reference to an objective this objective exends extends or continues with. This makes it easier to access related information.

The list of previous objectives is automatically rendered.

This is one way of keeping track of objectives from the past that will be worked on in this cycle. Another option is to delegate to a previous objective. Both techniques can be combined.

In case you need to organize objectives in a hierarchy then add additional objectives as children to this objective. Subordinate objectives will then be automatically listed.

Since objectives are typically short lived, there is probably no need to organize them for one OKR cycle in this way.

You may organize objectives in a hierarchy to signal which objectives are supporting parent objectives directly. These will be automatically listed in the section Supporting Objectives.

Note that a hierarchy is very strict since there is only one parent to an objective. This technique can help to structure a high-level objective to make it even more tangible by objectives that are aspected aspects of that objective.

An objective's parent may be another objective (probably defined at a higher level), a strategic theme (if there is no objective on a higher level to connect to), or a key result (if a key result at a higher level inspires the team to define a new objective). In case the connection to objectives, themes, or key results of another level is made, you probably need to replace the Parent Property Macro with a link to the respective instance this objective is connected to.