> For the complete documentation index, see [llms.txt](https://guides.tability.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.tability.io/docs/playbooks/cascade-your-okrs-to-more-teams.md).

# Cascade your OKRs to more teams

Extend your company OKRs to more teams: design the plan structure, draft team OKRs that ladder up, and link them in Tability so progress rolls up.

To start, share this page with your AI assistant and say:

> Run this playbook

The instructions below are for your assistant. You don't need to read or copy them.

### Instructions for AI assistants <a href="#instructions-for-ai-assistants" id="instructions-for-ai-assistants"></a>

If the user shares this page (or an article linking to it) and asks you to run it, follow the steps below from start to finish. If they only ask you to read, summarize, or edit it, do that instead.

#### Ground rules <a href="#ground-rules" id="ground-rules"></a>

* Ask one short question at a time. Propose a plan structure within five questions. Reuse anything the user has already told you.
* Confirm before touching a Tability workspace. Only use a workspace the user gives you by URL. Show its name and ID and get a yes before reading from it or writing to it.
* Don't cascade top-down by default. Never turn company key results into team objectives automatically. Teams set their own OKRs aligned to company goals.
* Keep plans focused. Link goals across plans instead of merging plans to avoid silos.
* Keep team OKRs small. Default to one objective and three outcome-focused key results per team.
* Don't make up numbers. If a baseline is unknown, say so. Label figures as measured, estimated, or proposed.
* Keep the user in charge. Get approval for the structure before building it, and for each team's OKRs before creating them. Draft messages for the user to send; don't message anyone else.
* Never change permissions yourself. Give the user the steps for anything private.
* Verify what you write. Read plans, goals, and relationships back before saying they worked.
* If something is blocked, keep the work done so far, tell the user the exact next step, and carry on with what you can.

#### 1. Set the scope <a href="#id-1-set-the-scope" id="id-1-set-the-scope"></a>

Start with a brief intro and ask:

> Which Tability workspace and company plan are we extending? Share the workspace URL and the plan's name or link.

Confirm the workspace and read the company plan. If there isn't one yet, stop and tell the user to set company goals first. Then ask only what you still need, such as:

* Which teams to add this cycle.
* How long the organization has run OKRs.
* The cycle to plan for. Default to the next quarter.
* Whether team leads will draft their own OKRs, or want you to draft starting points for them to edit.

If the organization is new to OKRs and wants to add everyone at once, recommend a T-shaped rollout instead: the leadership team plus one full department. Let the user choose.

#### 2. Map how teams work <a href="#id-2-map-how-teams-work" id="id-2-map-how-teams-work"></a>

Read workspace members and reporting lines. For each team in scope, find out (from the data or by asking):

* Who meets together to discuss goals.
* Whether any goals run on a different timeline from the rest (for example, annual goals beside quarterly ones).
* Whether any goals are sensitive and must stay private.
* Whether the organization works by department, by business unit, or around a few cross-functional priorities.

#### 3. Design the plan structure <a href="#id-3-design-the-plan-structure" id="id-3-design-the-plan-structure"></a>

Propose one structure, matched to how the organization works:

* **Company + departments:** a company plan with department sub-plans, and team sub-plans below if needed.
* **Business units:** a plan per unit, with team sub-plans if needed.
* **Big rocks:** a plan per cross-functional priority.

Apply these rules:

* One plan per group of people who meet to discuss those goals.
* A goal on a different timeline gets its own plan, linked into the plan where people expect to see it.
* Sensitive goals go in a separate private plan, linked into the public plan. Linked goals keep their original plan's privacy.
* Never merge plans to avoid silos. Link goals across plans instead.
* If a plan would no longer feel like it belongs to one group, split it.

Show the structure as a tree with plan names, timelines, and visibility. Ask the user to approve or change it before drafting any goals.

#### 4. Draft team OKRs and connect them <a href="#id-4-draft-team-okrs-and-connect-them" id="id-4-draft-team-okrs-and-connect-them"></a>

For each team, start from the company goals the team can influence, not from the company key results themselves.

* If team leads are drafting: give the user a short brief for each team with the company goals it can influence, the one-objective, three-key-result default, and a reminder that key results measure outcomes, not output.
* If you're drafting: write one objective and three key results per team, each with a baseline (or "unknown"), target, owner, and the company goal it supports. Put work items under them as initiatives.

Once all drafts are in, review them side by side and propose fixes for:

* **Overlap:** teams working toward the same result. Propose a dependency or related link, and name the shared work.
* **Duplicates:** the same goal in two plans. Keep it in one and link it into the other.
* **Conflicts:** teams pulling in opposite directions. Ask the user to settle them.
* **Gaps:** company goals no team is working toward, and goals that support nothing.

Then pick the company key results that should be calculated from team key results (for example, company revenue from Sales and Customer Success targets). For each, propose a roll-up: values with Sum or Average when units match, or percentages with Average or Latest when they don't.

Save everything as {company-name}-{cycle}-okr-rollout.md, marked Draft, using the outline at the end of this page. Share it with a short summary of the structure, team OKRs, links, and roll-ups, and ask whether they approve or want changes. Once approved, mark it Approved and move straight on to setup.

#### 5. Set it up in Tability <a href="#id-5-set-it-up-in-tability" id="id-5-set-it-up-in-tability"></a>

In the confirmed workspace, and without duplicating anything that already exists:

1. **Plans.** Create each plan with its timeline, nested under its parent as a sub-plan.
2. **Goals.** Add each team's objectives, key results (called "outcomes" in the API), and initiatives. Assign owners to real workspace members and leave unknown baselines empty.
3. **Alignment.** Link each team key result to the company objective or key result it supports.
4. **Dependencies.** For each roll-up, add the contributing team key results as dependencies of the company key result. Related links don't count toward a roll-up.
5. **Private plans.** Give the user the steps: open the plan, select the lock icon, choose Keep this plan private, and add editors and viewers.
6. **Roll-up settings.** If the roll-up type can't be set through the API, give the user the steps: open the parent key result, select ... > Edit, choose Rollup dependencies on the Target tab, pick the rollup type and method, enter the target and starting value for value roll-ups, check the preview, and save. Auto-sync needs a Premium workspace.

Read every plan, goal, and relationship back. Add record links to the rollout file.

#### 6. Prepare the rollout <a href="#id-6-prepare-the-rollout" id="id-6-prepare-the-rollout"></a>

Draft these for the user to send:

* A kickoff message for each team that explains the company goals, how the team's work feeds them, and how check-ins work.
* A short request to each team lead to review their OKRs and other teams' goals, and to comment where they see overlap or conflict.

Ask who will own the process: someone who watches for missing updates and goals that need attention. Suggest naming an OKR champion in each team to answer questions.

Ask whether they want a weekly scan. If yes and this tool can run scheduled tasks, create one that checks for missing check-ins and for team key results that put a company key result at risk, and give it the rollout file and everything it needs, since it won't remember this conversation. It should only notify the process owner when something needs attention. If scheduling isn't available, give them a prompt to run themselves.

#### 7. Wrap up <a href="#id-7-wrap-up" id="id-7-wrap-up"></a>

Mark the rollout file Final and share it with a short summary: links to each plan, the roll-ups and whether they're calculating, the steps the user still needs to do (permissions, roll-up settings), the drafted messages, the process owner and schedule, and any conflicts still open.

#### Rollout file outline <a href="#rollout-file-outline" id="rollout-file-outline"></a>

```markdown
# {Company}: {cycle} OKR rollout

Status · Cycle dates · Workspace · Teams in scope · Rollout type (full or T-shaped)

## Summary

## Plan structure (tree with timelines and visibility)

## Team OKRs and the company goals they support

## Links: overlaps, duplicates, and dependencies

## Roll-ups (parent, contributors, type, method)

## Conflicts and gaps

## Steps left for the user

## Rollout messages

## Process owner, champions, and schedule

## Tability records (links)
```

END OF PLAYBOOK
