# Align teams and cascade goals

## Overview

If you're using OKRs, you likely have a structure with multiple layers of goals. Ex:

***

📁 Company OKRs

    \|- 📁 Department OKRs

            \|- 📁 Team A OKRs

            \|- 📁 Team B OKRs

***

Tability will make it easy to replicate this approach. You will have simple tools to visualise alignment with the **Strategy Map**, and you will be able to see direct relationships between outcomes/key results in the **Cascading Map**.

## Video introduction

Watch the video below to understand how to align and cascade goals and OKRs in Tability.

{% embed url="<https://www.loom.com/share/08c2bdd67404401c8178b60eeb35c073>" %}

## Aligning plans with the Strategy Map

<figure><img src="https://318707989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMULqjSmZyGczPy2I6FGH%2Fuploads%2FLgxWAk1FKrYLufmsMxJm%2FGroup%2066.png?alt=media&#x26;token=37b121c7-ef7f-47bc-89d0-dc05182d2c72" alt=""><figcaption></figcaption></figure>

Organising company, department, and team goals/OKRs in a tree structure will allow Tability to display a complete **Strategy Map** that shows you every plan in progress in a single view.

You'll be able to:

* Compare the focus of your teams to make sure they are aligned
* See progress and confidence data across your org
* Quickly identify the goals and teams that are at risks
* Click on any outcome/key result to get more details

### Using the Strategy Map: it's automated!

The **Strategy Map** view is fully automated. Plans will automatically appear if they are in progress or coming up, and the relationships between plans will follow the structure of your workspace.

How to create your own Strategy Map:

1. Create a top-level plan for your company OKRs
2. From there, create sub-plans, for the different departments and teams
3. Optional: click on the plan icon to change it with something recognisable

At that stage your Plans section should look like this 👇

<figure><img src="https://318707989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMULqjSmZyGczPy2I6FGH%2Fuploads%2FYdOj935eFJnsUPuLUsDc%2FGroup%2065(1)(1).png?alt=media&#x26;token=a0b32472-067b-4856-b506-271e434be8a1" alt=""><figcaption></figcaption></figure>

Now you can simply click on the *Strategy Map* link in your sidebar to see all your plans in a map view.

<figure><img src="https://318707989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMULqjSmZyGczPy2I6FGH%2Fuploads%2FibIbnX53kYxpMYUwIJ8e%2Fstrategy-map-zoomed-in(1).png?alt=media&#x26;token=dd0ac10d-b338-444a-b96b-d6d2a66ac026" alt=""><figcaption></figcaption></figure>

This view makes it easy to compare the general direction of your teams and see at a glance when things are getting off-track.

{% hint style="info" %}
The Strategy Map only displays plans that are in progress or that are starting at a later date. It will automatically be updated when a new cycle starts!
{% endhint %}

## Cascade goals with the Cascading Map

<figure><img src="https://318707989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMULqjSmZyGczPy2I6FGH%2Fuploads%2FPNT2my0JeUcvcWFBb3IC%2FGroup%2067.png?alt=media&#x26;token=ecfa9a07-28a7-4125-b73b-26ff0fc5f01c" alt=""><figcaption></figcaption></figure>

You can go one step further and create direct relationships between your outcomes/key results. Once connected, you can see a cascading view of your goals by going to a plan and accessing the Cascading Map view for that plan.

The Cascading Map view will show you all the outcomes/KRs in that particular plan, as well as their dependencies.

Here's how you can re-create a similar view in your workspace.

1. Organise your goals/OKRs in layers using plans and sub-plans (see previous section)
2. Click on a specific outcome/key result
3. In the right side of the KR panel, click on *Add relationship*
4. Use the form to add a parent or a dependency

<figure><img src="https://318707989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMULqjSmZyGczPy2I6FGH%2Fuploads%2FxAFboqu8qS4tMH8yuLWY%2Frelationship-form.png?alt=media&#x26;token=10b8151e-b958-4d21-8569-0aa1dbf08532" alt=""><figcaption></figcaption></figure>

Repeat that operation with all the outcomes/key results that need to be connected (each team can do this quickly for the KRs they own).

Once you're done, go to the top-level plan, and click on the *Map* tab to load the **Cascading Map**.

<figure><img src="https://318707989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMULqjSmZyGczPy2I6FGH%2Fuploads%2FUqRdONb6WqnXuShuh2Yu%2Fcascading_tab.png?alt=media&#x26;token=c0da1c40-5cdd-4308-9ed5-de349f28d96a" alt=""><figcaption></figcaption></figure>

That's it! The cascading map will load 2 levels of outcomes/key results by default, but you can further expand any item that has dependencies.

<figure><img src="https://318707989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMULqjSmZyGczPy2I6FGH%2Fuploads%2FONQsrz3jn87P5FqQWht6%2Fcascading_map(1).png?alt=media&#x26;token=eb9b89d7-15fe-47ee-a00f-76b16645ddd5" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Some notes about the plan **Cascading Map**:

* The cascade will always start with the current plan. For example, displaying the cascading map of a sub-plan will not load the plan parent.
* Start with a top-level plan to visualise cascading dependencies through your org.
  {% endhint %}