---
name: okr-goal-framework-builder
description: Build OKRs or a goal framework that connects ambitious objectives to measurable key results. Use this skill whenever a user wants to set OKRs, build a goals framework, define objectives and key results, align a team on outcomes, or says 'set our OKRs', 'we need quarterly goals', or 'our goals are vague'. Trigger whenever ambitions need to become measurable, aligned objectives the team can execute against.
---

# OKR and Goal Framework Builder

## What this does and why it matters
Vague goals ("grow revenue", "improve marketing") produce vague effort. This skill builds objectives and key results that pair an ambitious, qualitative objective with measurable outcomes, so a team knows what winning looks like and can tell if they are getting there. Good OKRs align effort to outcomes instead of activity.

## Inputs to gather
1. The mission or the higher-level goal these OKRs serve.
2. The team or function and its scope.
3. The timeframe (usually a quarter).
4. Where the team is now on the relevant metrics.

## Method

### 1. Write objectives that are qualitative and ambitious
An objective is a memorable, inspiring statement of what to achieve, not a metric. It answers "where do we want to be?".

### 2. Make key results measurable outcomes, not tasks
Each objective gets two to four key results, each a measurable result (a number moving from X to Y), not an activity. "Ship the new page" is a task; "lift landing-page conversion from 2 to 4 percent" is a key result. This distinction is the whole point of OKRs.

### 3. Set outcomes, not outputs
Key results should measure the outcome that matters, not the work done. Doing the work but missing the outcome should register as a miss.

### 4. Calibrate ambition
OKRs should stretch. If the team is confident of 100 percent, they are sandbagged; roughly 70 percent achievement on a genuine stretch is healthy. Note the intended ambition level.

### 5. Keep focus
A few objectives at most. Ten objectives is a to-do list, not a strategy.

### 6. Connect up and across
Show how these ladder up to the higher goal and where they depend on other teams.

## Output format
ALWAYS use:

# OKRs: [Team] | [Timeframe]
## Objectives (2 to 4, qualitative and ambitious)
For each:
### Objective: [statement]
- KR1: [metric from X to Y]
- KR2: ...
## How these ladder up to [higher goal]
## Dependencies on other teams
## Ambition note (stretch level)

## Anti-patterns to avoid
- Key results that are tasks or outputs, not measurable outcomes.
- Too many objectives, so nothing is a priority.
- Sandbagged targets the team will obviously hit.
- Objectives that are just metrics with no inspiring "why".

## Example
An objective "become the obvious choice for mid-market AI adoption" pairs with key results moving qualified pipeline from a baseline to a target, lifting win rate, and hitting a content-authority metric, set as a stretch.