# How does Tability work?

Tability bridges the gap between strategy and execution, empowering teams to understand priorities and make a meaningful impact.

Founded by former Atlassian employees, Tability is built with execution at the core of the product with an emphasis on usability, functionality, and simplicity.

## Where does Tability sit?

Tability is the missing link between your strategy documents and your projects.

It gives you a complete platform to set quarterly goals, see progress trends, and map outcomes to outputs.

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

## How does Tability work?

Tability is a complete collaboration platform centered around outcomes and helps follow a simple goal setting process:

* **Set goals:** Use Tability's goal-setting AI and editor to set measurable goals for the quarter and save time.
* **Track goal progress:** Use weekly check-ins to update your goal metrics, confidence in completing them, and useful context to see trends and solve issues.
* **Align and cascade your goals:** Use the Strategy Map and the Cascading Map to align teams and see dependencies between goals.
* **Track strategic initiatives and projects:** Generate relevant initiatives for your strategy and provide regular status updates.
* **Explore your organization's progress:** Use filters to isolate the data that you care about.
* **Present and share your goal updates:** Share health digests with stakeholders and embed Tability views in your docs.

## Tability structure

### Workspaces

Your **workspace** is your org's home where you'll track goal, manage initiatives and collaborate with your team. All of your org's work will exist in inside of your Tability workspace

### Plans

The first thing you'll do after creating a workspace is to add your first plan.

A plan is a container for your goals and you will be able to organise your workspace with plans and sub-plans.

Generally, a plan will correspond to a specific team and quarter.

For instance, an org that has both company-level OKRs and OKRs for the Marketing team in Q4 will create 2 plans as shown below 👇

{% hint style="info" %}
📁 Company OKRs 2023 Q4

\|-- 📁 Marketing OKRs 2023 Q4
{% endhint %}

Each plan will have a specific timeline which will determine when check-ins should be active.

### Goals

After creating a plan, you'll be able to set your goals. The terminology that you use is up to you, but our defaults are:

* **Objectives:** What you're overall trying to achieve. Use objectives to group measurable outcomes together.
* **Outcomes:** Measurable goals that tell you if you've achieved your Objective. Use outcomes to set your targets and assign owners. If you're using OKRs, your outcomes will be your key results.
* **Initiatives:** The projects and tasks you're doing to push your outcomes forward. Use initiatives to capture the work that needs to be done to achieve your goals.

### Check-ins

After you've published your plan with your goals, your team will be asked to update their outcomes or key results each week with their progress. Check-ins track three things:

* **Metrics:** How are you tracking towards your measurable goals?
* **Confidence:** How confident is your team on being able to complete this outcome?
* **Analysis:** Why do or don't they feel confident? What progress have they made and what blockers are they encountering?

After the check-ins have been completed, Tability will automatically chart their responses so you can see how things have changed overtime. Everyone in your workspace can see the check-in details, so nothing gets siloed!

###


---

# 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/readme/how-does-tability-work.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.