> 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/build-your-brag-sheet-from-your-okrs.md).

# Build your brag sheet from your OKRs

Turn your goals, check-ins, and results in Tability into a brag sheet for your next review, promotion case, or raise conversation.

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 within four 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.
* Work only on the user's own record. Use goals they own or contributed to. Don't read or quote other people's check-ins unless they show the user's contribution, and never present others' work as the user's.
* Stay read-only. Don't write anything to Tability.
* Don't inflate or make up results. Use the numbers in the record. Label any figure the user supplies as "from you" and anything you estimate as estimated.
* Be selective. Lead with two to three of the highest-impact key results per quarter, not everything.
* Keep it private. Don't message anyone or share the brag sheet. The user decides who sees it.
* No negotiation figures from memory. Don't state salary benchmarks or market rates unless the user provides them or you can cite a current source.
* 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 purpose <a href="#id-1-set-the-purpose" id="id-1-set-the-purpose"></a>

Start with a brief intro and ask:

> What's this brag sheet for (a performance review, promotion case, or raise conversation), and what period should it cover?

Then ask only what you still need, such as:

* The Tability workspace URL, and the user's name or email in it.
* For a promotion case, the role they're aiming for and its competencies or job description, if they have them.
* Anything they did that isn't in Tability (projects, praise, side work) that they want included.

#### 2. Gather the record <a href="#id-2-gather-the-record" id="id-2-gather-the-record"></a>

Confirm the workspace and find the user's membership. Across every plan in the period, collect the key results and initiatives the user owned or contributed to, with:

* Start value, target, final value, and score.
* Every check-in by the user, with date, value, confidence, and comment.
* What each key result linked up to: parent objectives, company goals, and related or dependent goals in other teams' plans.
* Any retrospectives on those plans that mention the user's goals.

Also note these patterns:

* How consistently the user checked in.
* Where the user worked with other teams, @mentioned people, or escalated a blocker, with dates.
* Key results the user turned around (red or yellow to green), and stretch targets hit.

If the user has no goals in the period, say so and ask whether to work from what they tell you instead.

#### 3. Pick the strongest evidence <a href="#id-3-pick-the-strongest-evidence" id="id-3-pick-the-strongest-evidence"></a>

For each quarter, choose two to three key results the user owned or directly influenced, ranked by business impact and how much the user's work moved them. Leave the rest in an appendix.

For each chosen key result, work out its business impact:

* If the metric is a business result (revenue, retention, cost), state the change in numbers.
* If it isn't, follow its links up to the company goal it fed, and state what that work enabled (for example, a smaller backlog that let new products launch).

Show the user the shortlist with one line on why each made it, and ask them to confirm or swap. Ask what's missing from the record.

#### 4. Draft the brag sheet <a href="#id-4-draft-the-brag-sheet" id="id-4-draft-the-brag-sheet"></a>

For each chosen key result, write a short story:

* Where it started, where it ended, and the share of the target reached.
* What the user did: projects completed, milestones hit, and metric changes.
* What they overcame: blockers and how they resolved them.
* The business impact from step 3.

Then write a patterns section showing consistent strengths, with dated examples: cross-team work, leadership, early escalation, turnarounds, and consistent updates.

End with the ask, tied to the evidence:

* For a raise, connect the impact on company metrics to the request. Leave the figure to the user.
* For a promotion, map what they did to each competency of the target role.

Frame shortfalls as lessons and what changed next, not as excuses. Save it as {name}-brag-sheet-{period}.md using the outline at the end of this page. Share it with a short summary and ask for changes. Keep it to one page plus the appendix.

#### 5. Prepare the conversation <a href="#id-5-prepare-the-conversation" id="id-5-prepare-the-conversation"></a>

Give the user:

* A three-sentence opening that names their top results and their ask.
* The questions their manager is likely to ask, each with a short answer drawn from the brag sheet.
* Two or three gaps in the record a manager might raise, with an honest way to address each.

#### 6. Keep it current and wrap up <a href="#id-6-keep-it-current-and-wrap-up" id="id-6-keep-it-current-and-wrap-up"></a>

Give the user these two templates to make the next brag sheet easier:

**Weekly check-in comment**

> Last week we \[work done toward the goal]. This moved our metric from \[start] to \[now], which is \[what we hoped for / just OK / not what we wanted]. Next week we're going to \[planned work], which should \[keep momentum / get us back on track]. I need \[what you need, @mention who] to succeed this week.

**End-of-quarter summary**

> This quarter we went from \[start] to \[end], which was \[XX]% of our goal. While working on this key result, we \[projects, milestones, metric changes]. To get there, we had to overcome \[blockers], which we did by \[actions]. Next quarter we'll start \[improvement], stop \[what didn't work], and keep \[what went well].

Ask whether they want the brag sheet kept current. If yes and this tool can run scheduled tasks, create one that runs at the end of each quarter, adds that quarter's strongest key results and patterns to the brag sheet, and tells the user what it added. Give it the brag sheet file and everything it needs, since it won't remember this conversation. If scheduling isn't available, give them a prompt to run themselves.

Share the final brag sheet and a short summary: the key results it leads with, the ask, the conversation prep, the templates, and any schedule.

#### Brag sheet outline <a href="#brag-sheet-outline" id="brag-sheet-outline"></a>

```markdown
# {Name}: brag sheet, {period}

Purpose (review, promotion, or raise) · Period · Role · Workspace

## Summary

## Top results by quarter (story and business impact)

## Patterns and strengths (with dated examples)

## Lessons and growth

## The ask

## Conversation prep

## Appendix: other goals and sources (links)
```

END OF PLAYBOOK
