# Outcome/key result types

<div data-with-frame="true"><figure><img src="/files/85tFKxsr2jNheSmzCqJy" alt=""><figcaption></figcaption></figure></div>

## Overview

Outcomes (or key results) are how you and your team will measure your progress towards your objectives. These are almost always metric driven, meaning that you’re trying to improve or maintain a specific number.

In Tability, we have 7 different metric types to choose from to make sure that it’s as easy as possible for your team to track their progress:

* [#from-x-to-y](#from-x-to-y "mention") if you need to improve an existing metric
* [#stay-above-x](#stay-above-x "mention") if you need stay above a value
* [#stay-below-x](#stay-below-x "mention") if you need to stay below a value
* [#non-measurable](#non-measurable "mention") for non-measurable goals
* [#rollup](#rollup "mention") to rollup values from dependencies
* [#milestones](#milestones "mention") to track progress via initiatives
* [#measurable-without-a-target-legacy](#measurable-without-a-target-legacy "mention") for KPI-like metric (but this is getting retired)

{% hint style="info" %}
You can find and edit your Outcome Types by accessing the edit outcome modal. Learn more: [Editing outcomes/key results](/docs/become-a-tability-power-user/features/plans/editing-outcomes-key-results.md)
{% endhint %}

## From X to Y

The From X to Y outcome type is used when your goal involves progressing from a starting point to a specific target. For example: *Increase revenue by $200,000* or *Grow number of customers from 5k to 7.5k*.

<div data-with-frame="true"><figure><img src="/files/w0Ne3gDqRbEHhkN6aksM" alt=""><figcaption></figcaption></figure></div>

**How to use the fields**

* **Target:** expected value at the end of the cycle. Use this field to specify the format.
* **Starting at:** value at the start of the cycle

**How to format your metrics**

The target field uses smart formatting to detect the type of goal that you're tracking. You can write the number and the format in the same field (ex: `$100,000 MRR` , `7500 customers`, `20 NPS`...)

## Stay Above X

The Stay Above X outcome type is suitable for goals where you need to track a metric and ensure it remains above a certain threshold. For example: *Stay above 99.9% uptime* or *Maintain 15 or more accounts.*

<div data-with-frame="true"><figure><img src="/files/rcBNmJaGO32dpotiHGZ1" alt=""><figcaption></figcaption></figure></div>

**How to use the fields**

* **Stay above:** this is your target value
* **Baseline (optional)**: use the baseline to let Tability know when a metric is considering "off track". Baseline are required to estimate progress.

**How to use the baseline**

When setting this metric, you’ll have the option to include a baseline value.

The baseline value lets Tability calculate the amount of progress you’ve made towards your target should you fall below it.

For instance, lets assume that you're tracking CSAT and you want the following:

* Anything above CSAT 85% = great
* Anything below CSAT 50% = terrible

In this case you should set the `Stay above` value to be 85% and the `Baseline` to be 50%. Tability will then use this range to calculate the progress. For instance a CSAT at 70% would show as 57% progress on the goal.

{% hint style="info" %}
Without a baseline, Tability won’t include a percentage completion for goals with Stay above X metrics and they won’t be used to calculate your Objective’s completion percentage.
{% endhint %}

## Stay Below X

The "Stay Below" outcome type is ideal for goals that require tracking a metric and ensuring it remains below a specific threshold.

<div data-with-frame="true"><figure><img src="/files/YODrI8E5ZWHCHKjWzOj7" alt=""><figcaption></figcaption></figure></div>

The reverse of **Stay above X**, for when you want to maintain a metric below a certain level. For example: *Stay below 5% churn* or *Have 1 or fewer safety incidents in Q1*.\
\
As with the ***Stay above X*** metric, you’ll be able to set a baseline. For **Stay below X**, however, you’ll want to ensure that your baseline is **above** the target (so for Stay below 5% churn, you’d want your baseline to greater than 5%).

## Non-measurable

The **Non-measurable** outcome type is employed when you want to track a goal that doesn't have a clear metric attached to it. For instance: *Be on track for project X*, or *Make AI a priority for every team*.

<div data-with-frame="true"><figure><img src="/files/D6hct2YrTw43yHyYt1Ub" alt=""><figcaption></figcaption></figure></div>

Instead of tracking a specific score, the owner of the key result will simply report their confidence with an `on track`, `at risk`, or `off track` status.

<figure><img src="/files/yWQAx4tM1bzMaf8Obgg6" alt=""><figcaption></figcaption></figure>

These key results should be used sparingly as they are often tasks in disguise. Setting your key result to Confidence will strip out the metric entirely and have your team give you goal updates that are only the confidence (On track, at risk, and off track) and the comment. Good for binary key results (it’s been done or it hasn’t been done), these won’t be used to calculate progress towards your objective (since there is no metric at all).

## Rollup dependencies

The **Rollup dependencies** type will roll up the progress of the dependencies of a specific key result.

<div data-with-frame="true"><figure><img src="/files/FHfwgykhnknzBG3SdhAE" alt=""><figcaption></figcaption></figure></div>

**How to use this KR type**

1. Use [Outcome relationships](/docs/become-a-tability-power-user/features/outcomes-key-results/outcome-relationships.md) to link dependent KRs to your current key result
2. Select the rollup type. It can either be a rollup of the values or percentages
3. Select the rollup method (average, sum, latest value published)

## Milestone

**Milestone** key results will track progress using the attached initiatives. This is the perfect KR type to use if you have a list of tasks/projects to complete.

<div data-with-frame="true"><figure><img src="/files/FXozJQURuaSqwedFOq3V" alt=""><figcaption></figcaption></figure></div>

**How to use this**

Milestone progress is entirely based on the initiatives under the key result. When a user creates a new check-in, the progress value is automatically calculated based on the type of milestone.

There are 2 possible milestone types:

* **Count:** this will report the number of initiatives completed. Use this if you have a big backlog, but you're just trying to complete a certain number of items (ex: *Ship 20 experiments out of the idea backlog*)
* **Percentage:** this will track the percentage of initiatives completed. Use this if you have a clear plan, and you want every single item completed.

## Measurable without a target (legacy)

{% hint style="warning" %}
This type of key result will be soon retired and replaced by a complete KPI module
{% endhint %}

The **Measurable witout a target** KR type is used for goals where you are monitoring a metric without a specific target in mind. For example: *Understand our website conversion.*

<div data-with-frame="true"><figure><img src="/files/dvBhbQAkIGJMN6d4641j" alt=""><figcaption></figcaption></figure></div>

The **Measurable witout a target** metric doesn’t mean it won’t have a metric. This is useful when you want to measure what you’ve done, regardless of the overall outcome.

**Measurable witout a target** allows you to track the progression of the metric over time without having a specific goal in mind.

With **Measurable witout a target**, we also remove the confidence score, letting your team give updates on the goal that only include the metric and the comments. (Since there isn’t a set target, your team can’t be confident about whether they’ll achieve the goal.)

{% hint style="info" %}
Since your team can’t make a percentage progress towards a No Target metric, these key results won’t be used to calculate your Objective’s completion percentage.
{% endhint %}


---

# 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://guides.tability.io/docs/become-a-tability-power-user/features/outcomes-key-results/outcome-types.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.