# How to use tags for strategic pillars and MOALs

Tability is intentionally designed to stay simple: we prefer a small set of flexible concepts over many specialised fields.

Instead of adding separate fields for strategic pillars, MOALs, and other planning frameworks, we use tags to cover these needs in a lightweight way.

This keeps the product easier to learn, faster to adopt across teams, and still powerful enough for strategic reporting.

### Why this works

Many teams want to:

* Link org-level strategy (pillars/MOALs) to execution (Objectives/KRs)
* Filter all work tied to a specific MOAL or pillar
* Build dashboards grouped by strategic focus area

Tags solve this cleanly without introducing extra custom fields.

***

### Before you start

* Decide your official naming pattern (recommended below)
* Ask admins to manage/approve the official tag list
* Keep detailed MOAL/Pillar definitions in your knowledge base (Notion, Confluence, Google Docs, etc.)

***

### Step 1: Create official MOAL/Pillar tags

Create tags that represent your strategic references.

**Recommended naming format:**

* MOAL-1: \<short description>
* PILLAR-1: \<short description>

**Examples:**

* MOAL-1: Expand enterprise footprint
* PILLAR-2: Product reliability

{% hint style="info" %}
Best practice: restrict tag creation to admins so teams use one consistent set of strategic tags.
{% endhint %}

#### How to create your tags

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

1. Go to **Workspace settings > Manage Tags**
2. Toggle the tag restriction (if you want control over tag creation)
3. Click on **Create tag**
4. Create your pillars and MOAL tags

***

### Step 2: Tag the relevant Objectives and KRs

<figure><img src="/files/4FClone2MZQHQSDGwiT8" alt=""><figcaption></figcaption></figure>

Apply these tags to all related work items.

1. Open an Objective or KR.
2. In the details panel, find **Tags**.
3. Select the matching MOAL/Pillar tag.

Repeat for all Objectives, KRs, and initiatives you want included in strategic reporting.

***

### Step 3: Filter by MOAL/Pillar and save as a segment

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

Once items are tagged, create reusable filtered views.

1. Go to **Filters**.
2. Select the objectives or key results tab
3. Click **Filter +**.
4. Select **Tags**.
5. Choose the MOAL/Pillar tag.
6. Adjust the sorting option according to your preference
7. Click **Save segment**.

Use one saved segment per MOAL or pillar for fast reporting.

***

### Step 4: Build a strategy dashboard

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

Create a dashboard that shows each MOAL/Pillar with its linked work.

1. Go to **Dashboard**.
2. Click **Create dashboard**.
3. Name it (example: MOALs and Pillars).
4. Add a **Header** block for each MOAL/Pillar.\
   ![](/files/YAvTwu2RamNXt7YwQukf)
5. Under each header, add:

* **Objective list** widget and/or
* **Key Result list** widget\
  filtered to the corresponding tag.\
  ![](/files/QeHFhxGaYuVHCU8QICft) ![](/files/DGuFv8JSKtM1lwBPKcFH)

***

### Best practices

* Keep tag names short, structured, and searchable.
* Use one primary MOAL/Pillar tag per item when possible.
* Review tags periodically to avoid duplicates.
* Keep full strategic definitions outside Tability – use tags as references.

\ <br>


---

# 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/how-tos/how-to-use-tags-for-strategic-pillars-and-moals.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.