# Terminology

### Objective

An Objective is a description of a goal to be achieved in the future. An Objective sets a clear direction and provides motivation. In OKR methodology objectives should be hard to reach, but not impossible, goals.

### Key Result

A Key Result is a metric with a starting value and a target value that measures progress towards an Objective. While and Objective is like a destination on a map, a Key Result is like a signpost with a distance that shows you how close you are.

### Delivery Cycle

OKR delivery cycle is a time period used to add time constraint to your objectives. Cycles can be freely defined by your company. Typically a cycle lasts one quarter.

Example: 2018 1st Quarter

### Alignment

Objectives can be vertically or horizontally aligned. Alignment indicates support for another objective, usually owned by another team at your company. For example, a company objective to *Grow business* might be supported by Marketing team's objective *Create more leads*.

### Team

Teams can be set as objective owners. Objectives are generally large in scope and will have several people working on the objective in order to reach it. You can designate team responsibilities by assigning objectives to teams.

Example: Product Engineering Team

### Lead

Lead is a person who oversees an objective. Lead is a point person for any OKR related questions. Lead can be part of the team that owns the objective or someone completely outside the team.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.simpleokr.com/simple-okr-manual/objectives-and-key-results/terminology.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
