> 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/turn-your-long-term-goals-into-quarterly-okrs.md).

# Turn your long-term goals into quarterly OKRs

Turn the long-term plan, KPIs, and milestones you already have into a short set of quarterly OKRs, then track them in Tability.

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. Deliver a first draft of the OKRs within five questions. Reuse anything the user has already told you.
* Let the user name the business and team. Never assume it's Tability, this page's publisher, or whatever account or tools are connected.
* 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.
* Never change the long-term plan. Long-term targets, KPIs, and milestones stay where they are. Never copy a long-term target into an OKR.
* Keep the set small. At most three objectives, each with two to four key results. Fewer is fine.
* Don't make up numbers. If a baseline is unknown, say so. Label figures as measured, estimated, or proposed.
* Verify what you write. Read records and scheduled jobs back before saying they worked.
* Keep the user in charge. You draft; the user chooses the bets. Ask before changing targets, owners, or existing goals. Don't message anyone else.
* 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. Choose how to track <a href="#id-1-choose-how-to-track" id="id-1-choose-how-to-track"></a>

Start with a brief intro and ask:

> Would you like AI to automatically track progress on your OKRs and run regular check-ins, or would you prefer to track them yourself?

If they choose automatic tracking, check whether this tool can run scheduled tasks that use connected tools (for example, Claude Cowork or ChatGPT automations). If it can't, recommend one that can, and give the user a short message to paste there with their answers so far. They can also stay here and move tracking later.

#### 2. Collect the long-term plan <a href="#id-2-collect-the-long-term-plan" id="id-2-collect-the-long-term-plan"></a>

Ask:

> Which business or team are we writing OKRs for, and where does your long-term plan live? Share a link, a file, or paste the main targets.

Then ask only what you still need, such as:

* The long-term targets, with deadlines (for example, "$30M ARR in three years").
* This year's anchor for each target, if one exists.
* Where each target stands today.
* The KPIs the team already watches.
* Any milestones on the plan (launches, certifications, platform releases).
* The cycle to plan for. Default to the next quarter.
* Whether goals already exist in a Tability workspace (if yes, ask for its URL).

While you ask, read any plan, file, or connected tool the user points to, and check connected analytics, sales, billing, or project tools for current values. Make sure each source belongs to this business or team.

#### 3. Map the gaps <a href="#id-3-map-the-gaps" id="id-3-map-the-gaps"></a>

Build a working table of every long-term target and milestone with:

* Destination and deadline.
* Current value (or "unknown").
* Gap: the distance between today and where the target needs to be by the end of this cycle to stay on track.
* Trajectory: on track, behind, or unknown.
* Reason for the gap, in one line. Ask the user if you can't tell from the data.

Treat milestones as on track, at risk, or behind instead of a numeric gap.

#### 4. Pick what earns an OKR <a href="#id-4-pick-what-earns-an-okr" id="id-4-pick-what-earns-an-okr"></a>

Mark a target as an OKR candidate only if all three are true this cycle:

1. It won't improve enough on its current trajectory.
2. The team is willing to put real focus and resources behind it now.
3. The team can meaningfully move it within the cycle.

Also drop any candidate where the answer to "what would we do differently because this is an OKR?" is "nothing."

Recommend one to three candidates, ranked by how much gap they could close. Every other target stays a KPI or milestone on the plan. Show the user the shortlist, say in one line why each made it and why the closest misses didn't, and ask them to confirm or swap. Don't continue until they've chosen.

#### 5. Draft the OKRs <a href="#id-5-draft-the-okrs" id="id-5-draft-the-okrs"></a>

For each chosen target:

1. **Objective.** Name the single shift that would close the most gap this cycle, in plain language with no numbers. Base it on the reason for the gap, not on the target itself.
2. **Key results.** Write two to four outcomes that would prove the bet is working, each with a baseline (or "unknown"), target, deadline, owner, and data source.
3. **Initiatives.** List the work that drives each key result, with owners. Tasks such as "hire two reps" or "launch a partner program" go here, never in key results.
4. **Link.** Record which long-term target the objective serves.

For milestone-based targets, leave the milestone on the plan and write key results for whether it worked, not whether it shipped (for example, activated accounts, defect rate, or reference customers after a launch). If a milestone is low-risk and purely done-or-not, recommend leaving it as a milestone with no OKR.

Before sharing, check every OKR and fix any that fail:

* The long-term target's number does not appear in the objective or any key result.
* Each key result is an outcome. Test: could the team finish the work and still not move this number? If yes, it's a task.
* No more than three objectives and four key results each.
* Every key result has a measurable baseline or is marked "unknown" with a plan to measure it.
* Nothing duplicates a KPI the team already watches, unless the OKR is a deliberate push to move it.

Save the draft as {team-name}-{cycle}-okrs.md, marked Draft, using the outline at the end of this page. Share it with a short summary of the bets and what's staying a KPI or milestone, and ask whether they approve or want changes. Once approved, mark it Approved and move straight on to setup.

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

Ask for the Tability workspace URL to use (or confirm the one they already shared). If they don't have one, point them to sign up and connect Tability to their AI tool.

Confirm the workspace, then:

* Check whether the long-term targets already exist. If not, ask whether to add them: long-term targets as a long-term plan with objectives and key results, and the KPIs as KPIs. Don't create them without a yes.
* Create a plan for the cycle and add the OKRs:
  * Objectives → objectives
  * Key results → key results (called "outcomes" in the API)
  * Initiatives → initiatives
* Align each new key result to the long-term key result it serves, so the two plans stay linked without duplicating anything.

Assign owners to real workspace members, leave unknown baselines empty, and avoid duplicating anything that already exists. Add record links to the OKR file.

#### 7. Test the first check-in and set up reviews <a href="#id-7-test-the-first-check-in-and-set-up-reviews" id="id-7-test-the-first-check-in-and-set-up-reviews"></a>

Pull the current value for each key result you can reach, record a check-in in Tability with a one-line note, and confirm it saved. Tell the user which key results will need manual updates.

Automatic: create two scheduled tasks, and give each one the OKR file and everything it needs, since it won't remember this conversation.

* Check-in (weekly or fortnightly, to suit the data): update key results and flag risks or blockers. When something stalls, suggest changes to the work, not the target. Only notify the user when something needs attention.
* End-of-cycle review: score each key result, note what moved and what stalled, and ask which gaps still need an OKR next cycle. Use scores to prompt discussion, never to judge people.

Both should stop at the end of the cycle.

Manual: give the user a check-in prompt and an end-of-cycle review prompt they can run themselves.

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

Share the final OKR file and a short summary: links to the Tability plan, which long-term targets each objective serves, what stays a KPI or milestone, the first initiatives and owners, what the first check-in recorded, when reviews run, and anything the user still needs to do.

#### OKR file outline <a href="#okr-file-outline" id="okr-file-outline"></a>

```markdown
# {Team}: {cycle} OKRs

Status · Cycle dates · Timezone · Tracking (automatic or manual)

## Summary

## Long-term targets and gaps

## What earned an OKR, and what stays a KPI or milestone

## Objectives and key results (with the long-term target each serves)

## Initiatives and owners

## Open questions and data gaps

## Sources

## Tracking setup (links, schedules)
```

END OF PLAYBOOK
