# Strategy Map

If you're using OKRs, you likely have a structure with multiple layers of goals. It would look something like this:

* 📁 Company OKRs
  * 📁 Department OKRs
    * 📁 Team OKRs

Tability will make it easy for you to replicate the structure above and ensure that goals are aligned throughout your org. The platform embraces [an approach that reduces friction](https://www.tability.io/okrs/cascading-vs-aligning-okrs) and minimises the amount of work for your team.

### See how plans aligned with the Strategy Map

You can use plans and sub-plans to create your layers of goals and OKRs in Tability.

<figure><img src="/files/ZmOOTAq4yrK5BNJhmSdE" alt=""><figcaption><p>Strategy Map in Tability</p></figcaption></figure>

Organising your company, department, and team OKRs in a tree structure will allow Tability to display a complete Strategy Map where you can quickly compare the content of the plans of your different teams.

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 to a recognisable emoji or symbol

At that stage your Plans section should look like this 👇

<figure><img src="/files/oubeFbNuvsSwyBfqU5h0" alt=""><figcaption><p>Plan view in Tability</p></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="/files/hXCtN7s6nfzfNXzJNU87" 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.

<figure><img src="/files/gH2uCJvjLPAxAQh43aPM" alt=""><figcaption><p>Strategy Map in Tability</p></figcaption></figure>

{% hint style="info" %}
The **Strategy Map** only displays plans that are in progress or published starting at a later date. It will automatically update this view when a new cycle starts.
{% 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/plans/strategy-map.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.