OKR Builder

Purpose

Create aligned Objectives and Key Results (OKRs) for product teams with measurable key results and initiative mapping.

Input: Product vision, strategic priorities, time period (quarter), team scope
Output: OKR document with 1–3 objectives, 2–4 KRs each, and linked initiatives Examples: See examples.md for worked input/output.

Workflow

Step 1: Define planning context

Confirm:

• Time period (e.g., Q3 2026)
• Team/product scope
• Strategic themes from vision or leadership
• Constraints (headcount, dependencies)

Step 2: Draft objectives

Rules for objectives:

• Qualitative and inspirational
• Actionable by the team
• 1–3 objectives per team per period
• Aligned with product vision north star

Format: "Verb + ambitious outcome" (e.g., "Delight enterprise admins with effortless onboarding").

Step 3: Define key results

Per objective, 2–4 KRs:

KR rules:

• Measurable (number, percentage, binary)
• Outcome-based, not output-based ("launch feature" is not a KR)
• Ambitious but achievable (60-70% confidence)

Step 4: Map initiatives

Link epics/features to KRs:

Initiatives are hypotheses for achieving KRs.

Step 5: Check alignment

Verify:

• KRs ladder up to north star metric
• No conflicting KRs across objectives
• No more than 3 objectives (focus)

Step 6: Validate

Run Validation checklist.

Decision Rules

Validation

• 1–3 objectives defined
• 2–4 KRs per objective with baseline and target
• All KRs are measurable outcomes (not outputs)
• Initiatives mapped to KRs
• Alignment with north star noted
• Confidence level stated per KR (optional but recommended)
• No more than 3 objectives

Anti-patterns

• OKR as task list — "Ship v2", "Hire 2 engineers" as KRs.
• Too many objectives — 5+ objectives diluting focus.
• Sandbagging — 100% confident easy KRs.
• Unmeasurable KRs — "Improve quality" without metric.
• Orphan OKRs — no connection to vision or initiatives.

Best Practices

• Use OKR formula: "We will [objective] as measured by [KR1], [KR2]..."
• Review OKRs mid-quarter; don't change objectives lightly.
• Separate committed OKRs from aspirational stretch.
• Align with product/feature-prioritization for initiative selection.
• Grade KRs 0.0–1.0 at end of period; 0.7 is success.

Output Structure

# OKRs: [Team/Product] — [Period]

## Context
- **Vision alignment:** [north star connection]
- **Scope:** [team/product]

## Objective 1: [Statement]
| KR | Metric | Baseline | Target | Owner |
|----|--------|----------|--------|-------|

**Initiatives:**
- [Initiative] → KR 1.1

## Objective 2: [Statement]
[Same structure]

## Alignment Check
| North star | Supported by |
|------------|--------------|

## Scoring Guide
0.0 = no progress | 0.7 = success | 1.0 = exceeded

Next Skills