---
# === IDENTITY ===
id: business/startup-metrics/okr-setting-methodology/2026
canonical_question: "How do I set OKRs for a startup — quarterly framework, max 3 objectives, 3 key results each?"
aliases:
  - "Startup OKR setting methodology 2026"
  - "Quarterly OKR framework for startups"
  - "Objectives and key results implementation guide"
entity_type: execution_recipe
domain: business > startup-metrics > OKR Setting Methodology
region: global
jurisdiction: global
temporal_scope: 2025-2026

# === VERIFICATION ===
last_verified: 2026-03-12
confidence: 0.88
version: 1.0
first_published: 2026-03-12

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: evolving
  last_breaking_change: "OKR tooling landscape consolidated through 2025-2026 with AI-assisted tracking features becoming standard in Lattice, Quantive, and Weekdone"
  next_review: 2026-09-08
  change_sensitivity: high

# === CONSTRAINTS ===
constraints:
  - "Maximum 3 company-level objectives per quarter — exceeding this dilutes focus and reduces completion rates"
  - "Each objective must have exactly 2-3 measurable key results — more creates tracking overhead, fewer leaves blind spots"
  - "OKRs must not be tied to individual performance reviews or compensation — this kills psychological safety and ambitious goal-setting"
  - "Key results must be outcomes, not tasks — 'Increase activation rate from 45% to 60%' not 'Redesign onboarding flow'"
  - "Aspirational OKRs target 70% completion — if you hit 100% consistently, targets are not ambitious enough"
  - "OKR planning must start 2-4 weeks before the quarter begins to allow for alignment and iteration"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "User needs a high-level strategy for choosing which metrics to track"
    use_instead: "Search knowledgelib.io for north star metric selection — no dedicated unit yet"
  - condition: "User wants KPI dashboards, not goal-setting methodology"
    use_instead: "business/startup-metrics/dashboard-design-for-startups/2026"
  - condition: "User is at an enterprise with 500+ employees needing org-wide OKR rollout"
    use_instead: "org-wide OKR rollout at enterprise scale (500+ employees)"

# === AGENT HINTS ===
inputs_needed:
  - key: company_stage
    question: "What stage is the startup?"
    type: choice
    options: ["pre-product-market-fit", "post-PMF / scaling", "growth stage (Series B+)", "not sure"]
  - key: team_size
    question: "How many people are on the team?"
    type: choice
    options: ["1-5 (founding team)", "6-20 (early team)", "21-50 (growing team)", "50+ (scaling)"]
  - key: okr_experience
    question: "Has the team used OKRs before?"
    type: choice
    options: ["first time", "tried but failed", "some experience", "experienced"]
  - key: tool_preference
    question: "Which OKR tracking tool should be used?"
    type: choice
    options: ["spreadsheet (free)", "Weekdone", "Lattice", "Quantive", "no preference — auto-select"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "Company mission and current strategic priorities"
      source: "founder / leadership team"
      format: "document or verbal alignment"
    - name: "Current metrics baseline (revenue, users, retention, etc.)"
      source: "analytics / finance"
      format: "dashboard or spreadsheet"

  outputs:
    - name: "Quarterly OKR document"
      format: "spreadsheet or OKR tool"
      description: "3 company objectives with 2-3 key results each, cascaded to team-level OKRs"
    - name: "Weekly check-in template"
      format: "document or tool configuration"
      description: "Structured format for weekly confidence scoring and blocker identification"
    - name: "Quarter-end scorecard"
      format: "spreadsheet"
      description: "Scored OKRs (0.0-1.0) with retrospective notes and carry-forward decisions"

  tools_required:
    - name: "Google Sheets or Notion"
      purpose: "OKR drafting, tracking, and scoring"
      tier: free
      cost: "$0"
      alternatives: ["Weekdone", "Lattice", "Quantive"]
    - name: "Weekdone"
      purpose: "Dedicated OKR tracking with automated check-ins"
      tier: paid
      cost: "$9-11/user/month"
      alternatives: ["Google Sheets", "Lattice"]
    - name: "Lattice"
      purpose: "OKR management integrated with performance reviews"
      tier: paid
      cost: "$11/user/month"
      alternatives: ["Weekdone", "Quantive"]

  credentials_needed:
    - service: "Google Workspace"
      type: "Google account"
      where_to_get: "https://workspace.google.com"
      free_tier_limits: "Unlimited for Sheets/Docs"

  estimated_duration: "4-6 hours spread over 2 weeks (planning) + 30 min/week (check-ins) + 2 hours (quarter-end review)"
  estimated_cost: "$0 (spreadsheet) to $11/user/month (dedicated tool)"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/business/startup-metrics/okr-setting-methodology/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-12)"

# === RELATED UNITS ===
related_kos:
  feeds_into:
    - id: "business/startup-metrics/dashboard-design-for-startups/2026"
      label: "Startup dashboard design — metric selection and audience-specific views for founders, investors and teams"
  related_to:
    - id: "finance/industry-benchmarks/saas-industry-benchmarks-2026/2026"
      label: "SaaS industry benchmarks 2026 — CAC, LTV, NRR, churn and Rule of 40 by SMB/mid-market/enterprise segment (US VC-backed SaaS medians)"

# === SOURCES ===
sources:
  - id: src1
    title: "Measure What Matters — OKR Framework"
    author: John Doerr / What Matters
    url: https://www.whatmatters.com/faqs/okr-meaning-definition-example
    type: reference_book
    published: 2018-04-24
    reliability: authoritative
  - id: src2
    title: "How to Make OKRs Actually Work at Your Startup"
    author: First Round Review
    url: https://review.firstround.com/how-to-make-okrs-actually-work-at-your-startup/
    type: industry_guide
    published: 2024-01-15
    reliability: authoritative
  - id: src3
    title: "Radical Focus — OKR Methodology for Startups"
    author: Christina Wodtke
    url: https://cwodtke.com/
    type: reference_book
    published: 2021-09-01
    reliability: authoritative
  - id: src4
    title: "How to Write Effective OKRs — Lattice Guide"
    author: Lattice
    url: https://lattice.com/library/how-to-write-effective-okrs-plus-examples
    type: industry_guide
    published: 2025-01-10
    reliability: high
  - id: src5
    title: "OKR Planning: 8 Steps for Success"
    author: Weekdone
    url: https://blog.weekdone.com/okr-planning/
    type: industry_guide
    published: 2025-03-01
    reliability: high
  - id: src6
    title: "The OKR Cycle — Cadence Guide"
    author: Quantive (formerly Gtmhub)
    url: https://quantive.com/resources/articles/okr-cycle
    type: industry_guide
    published: 2025-06-01
    reliability: high
---

# OKR Setting Methodology for Startups

## Purpose

This recipe produces a complete quarterly OKR set for a startup: 3 company-level objectives with 2-3 measurable key results each, cascaded to team-level OKRs, with a weekly check-in cadence and quarter-end scoring process. The output is a living document that aligns every team member around the quarter's most important outcomes and provides a structured rhythm for tracking progress. [src1]

## Prerequisites
<!-- Agents: verify ALL prerequisites before executing. Missing prerequisites = failed execution. -->

- [ ] **Company mission and strategic priorities** articulated by leadership — even a one-paragraph statement of direction
- [ ] **Current metrics baseline** — know your current numbers for revenue, users, retention, NPS, or whatever you plan to improve
- [ ] **Team alignment on priorities** — leadership must agree on the top 1-3 problems to solve this quarter before drafting OKRs
- [ ] **OKR tracking tool** — Google Sheets (free), [Weekdone](https://weekdone.com) ($9/user/mo), [Lattice](https://lattice.com) ($11/user/mo), or [Quantive](https://quantive.com) (custom pricing)
- [ ] **Calendar blocks** — 2 hours for OKR drafting workshop, 1 hour for team cascade session, 30 min/week for check-ins

## Constraints
<!-- Hard rules. Agents: enforce throughout execution. Violating these = broken output or legal risk. -->

- Maximum 3 company-level objectives per quarter. More dilutes focus — research shows teams with fewer objectives achieve more. [src1]
- Each objective gets exactly 2-3 key results. Fewer than 2 leaves the objective unmeasurable; more than 4 creates tracking overhead. [src4]
- Key results must be outcomes (measurable changes in state), never tasks or activities. [src2]
- OKRs must not be tied to compensation or performance reviews — this is the single most common reason OKR programs fail at startups. [src3]
- Aspirational OKRs should target ~70% completion as success. Committed OKRs (must-do) target 100%. Label each objective as aspirational or committed. [src1]
- Planning must start 2-4 weeks before the quarter begins. Last-minute OKRs produce low alignment. [src5]

## Tool Selection Decision

<!-- Agent selects the right tool path based on user inputs.
     Each path leads to a different execution flow below. -->

```
Which path?
├── First-time OKR team AND budget = free
│   └── PATH A: Google Sheets — simple, visible, no learning curve
├── First-time OKR team AND budget > $0
│   └── PATH B: Weekdone — guided OKR workflow with coaching prompts
├── Experienced team AND budget = free
│   └── PATH C: Google Sheets + Notion — flexible custom tracking
└── Experienced team AND budget > $0
    └── PATH D: Lattice or Quantive — cascading, automated check-ins, analytics
```

| Path | Tools | Cost | Setup Time | Best For |
|------|-------|------|------------|----------|
| A: Sheets Free | Google Sheets | $0 | 30 min | Teams of 1-10, first OKR cycle |
| B: Guided Paid | Weekdone | $9-11/user/mo | 1-2 hours | Teams of 5-20, want structure |
| C: Flexible Free | Sheets + Notion | $0 | 1 hour | Experienced teams, custom needs |
| D: Full Platform | Lattice / Quantive | $11+/user/mo | 2-4 hours | Teams of 20+, need cascading |

## Execution Flow

### Step 1: Align on Company Direction (Week -2)

**Duration**: 1-2 hours
**Tool**: Whiteboard / document

Gather the leadership team (founders + leads). Answer three questions:

1. **Where are we now?** Review current metrics, recent wins, recent failures.
2. **Where do we need to be in 90 days?** Identify the 1-3 most important shifts.
3. **What will we NOT focus on?** Explicitly name what gets deprioritized.

Write a one-paragraph "quarter theme" that captures the strategic direction. This is not an OKR — it is the context that makes OKRs coherent. [src2]

```
Example quarter theme:
"Q2 2026: Prove retention before scaling acquisition.
We have 2,000 users but 60-day retention is 22%. Until we reach 40% retention,
growth spending is paused. All teams orient around activation and retention."
```

**Verify**: Every leader can explain the quarter theme in one sentence without reading it.
**If failed**: The theme is too complex. Simplify to one primary focus.

### Step 2: Draft 3 Company Objectives (Week -2)

**Duration**: 1-2 hours
**Tool**: Collaborative document or whiteboard

Using the quarter theme, draft exactly 3 company-level objectives. Each objective must be: [src1]

- **Qualitative** — describes a desired state, not a number
- **Inspirational** — people should feel motivated reading it
- **Time-bound** — implicitly scoped to the quarter
- **Actionable** — the team can influence the outcome directly

```
Format: "Objective [N]: [Qualitative statement of desired outcome]"

Example:
Objective 1: Make our product so sticky that users come back without prompting
Objective 2: Build a repeatable sales motion for mid-market accounts
Objective 3: Establish engineering velocity that ships weekly without breaking things
```

Label each objective as **Aspirational** (stretch — 70% completion = success) or **Committed** (must-do — 100% expected). Most startup OKRs should be aspirational. [src1]

**Verify**: You have exactly 3 objectives. Each is qualitative, memorable, and directly tied to the quarter theme.
**If failed**: If you have more than 3, force-rank and cut. If fewer than 3, the quarter theme may be too narrow.

### Step 3: Define 2-3 Key Results Per Objective (Week -2 to -1)

**Duration**: 2-3 hours
**Tool**: Spreadsheet or OKR tool

For each objective, write 2-3 key results. Every key result must follow this formula: [src4]

```
Key Result format: "[Verb] [metric] from [baseline] to [target] by [end of quarter]"

Example for Objective 1 (retention focus):
KR 1.1: Increase 60-day retention from 22% to 40%
KR 1.2: Improve Day-1 activation rate from 35% to 55%
KR 1.3: Reduce time-to-value from 12 minutes to under 4 minutes
```

Key result quality checklist: [src2]
- Is it a measurable outcome, not a task? (Yes/No)
- Do I know the current baseline? (Yes/No)
- Is the target ambitious but not delusional? (Yes/No)
- Can we measure progress weekly, not just at quarter-end? (Yes/No)
- Is it within our team's control to influence? (Yes/No)

If any answer is "No", rewrite the key result.

**Verify**: 3 objectives x 2-3 KRs each = 6-9 total key results. Every KR has a baseline, target, and is measurable weekly.
**If failed**: If a KR has no baseline, spend time establishing the measurement before finalizing. No baseline = no OKR.

### Step 4: Cascade to Team OKRs (Week -1)

**Duration**: 1-2 hours per team
**Tool**: Same as company OKR tool

Each team (product, engineering, sales, marketing, etc.) creates their own OKRs that ladder up to company objectives. The cascading model: [src4]

```
Cascading approach:
├── STRICT alignment (recommended for first-time OKR teams):
│   Company KR 1.1 → becomes Team Objective 1 → Team writes their own KRs
│   Company KR 1.2 → becomes Team Objective 2 → Team writes their own KRs
│
└── DIRECTIONAL alignment (for experienced OKR teams):
    Teams write objectives that clearly support company objectives
    but don't mirror them word-for-word — more autonomy
```

Rules for team OKRs:
- Maximum 3 team objectives (same cap as company level)
- 2-3 key results per team objective
- At least one team KR must directly map to a company KR
- Teams present their draft OKRs to each other to catch conflicts and dependencies [src2]

**Verify**: Every company KR has at least one team OKR that directly drives it. No orphaned company KRs.
**If failed**: Identify which company KR has no team ownership. Either assign it or reconsider whether it is achievable this quarter.

### Step 5: Establish Weekly Check-in Cadence (Week 1)

**Duration**: 30 minutes/week ongoing
**Tool**: OKR tool or structured meeting

Set up a weekly OKR check-in (Monday or Friday, 30 minutes max). The format: [src5] [src6]

```
Weekly OKR Check-in Template:

For each Key Result:
1. Current value: [number]
2. Confidence score (1-10): [score]
   - 8-10: On track
   - 5-7: At risk — needs attention
   - 1-4: Off track — needs escalation
3. What moved the needle this week: [1-2 sentences]
4. Biggest blocker: [if any]
5. Help needed: [specific ask, if any]
```

Confidence scoring is the single most valuable OKR practice. It forces honest assessment every week instead of waiting for a quarter-end surprise. [src6]

**Verify**: First check-in is scheduled and the template is distributed to all participants.
**If failed**: If people skip check-ins, reduce the meeting to 15 minutes and make it async (written updates in Slack or the OKR tool).

### Step 6: Score and Retrospect at Quarter-End (Week 12-13)

**Duration**: 2-3 hours
**Tool**: Spreadsheet + meeting

At the end of the quarter, score every key result on a 0.0-1.0 scale: [src1]

```
Scoring scale:
0.0 - 0.3: Failed to make meaningful progress
0.4 - 0.6: Made progress but fell significantly short
0.7 - 0.9: Delivered strong results (sweet spot for aspirational OKRs)
1.0:        Fully achieved (expected for committed OKRs only)

Overall Objective score = average of its Key Result scores
Overall Company score = average of all Objective scores
```

Quarter-end retrospective questions:
1. Which objectives scored highest? Why?
2. Which scored lowest? What blocked progress?
3. Were any OKRs wrong in hindsight — wrong target, wrong metric, wrong priority?
4. What should carry forward to next quarter?
5. What new information changes our direction?

**Verify**: All KRs scored, retrospective documented, and carry-forward decisions made before next quarter's planning begins.
**If failed**: If scoring is delayed beyond 1 week after quarter-end, it loses value. Time-box the scoring to a single 2-hour session.

## Output Schema

<!-- Exact format of the deliverable. Downstream agents and dashboard cards
     reference this schema to consume the output. -->

```json
{
  "output_type": "quarterly_okr_set",
  "format": "spreadsheet or OKR tool",
  "columns": [
    {"name": "level", "type": "string", "description": "company or team name", "required": true},
    {"name": "objective_number", "type": "number", "description": "1-3", "required": true},
    {"name": "objective_text", "type": "string", "description": "Qualitative objective statement", "required": true},
    {"name": "objective_type", "type": "string", "description": "aspirational or committed", "required": true},
    {"name": "kr_number", "type": "string", "description": "e.g., 1.1, 1.2, 2.1", "required": true},
    {"name": "kr_text", "type": "string", "description": "Key result with metric, baseline, and target", "required": true},
    {"name": "baseline", "type": "number", "description": "Current value of the metric", "required": true},
    {"name": "target", "type": "number", "description": "Target value by end of quarter", "required": true},
    {"name": "owner", "type": "string", "description": "Person or team responsible", "required": true},
    {"name": "confidence", "type": "number", "description": "Weekly confidence score 1-10", "required": false},
    {"name": "final_score", "type": "number", "description": "Quarter-end score 0.0-1.0", "required": false}
  ],
  "expected_row_count": "6-27",
  "sort_order": "level (company first, then teams), then objective_number",
  "deduplication_key": "level + kr_number"
}
```

## Quality Benchmarks

<!-- How to evaluate if the output is good enough.
     Links to benchmark cards where applicable. -->

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| Company objectives count | Exactly 3 | Exactly 3 | Exactly 3 |
| Key results per objective | 2 | 3 | 3 with leading + lagging mix |
| KRs with quantitative baselines | > 70% | > 90% | 100% |
| Team OKR coverage of company KRs | > 60% | > 80% | 100% — every company KR owned |
| Weekly check-in attendance | > 50% of weeks | > 75% of weeks | > 90% of weeks |
| Quarter-end scoring completion | Scored within 2 weeks | Scored within 1 week | Scored same week as quarter-end |

**If below minimum**: Re-run Step 3 to strengthen key results. If check-in attendance is low, switch to async written updates and shorten the meeting cadence.

## Error Handling

<!-- Common failures and recovery actions. Agents need this to handle
     execution errors without human intervention. -->

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| More than 3 objectives drafted | Team cannot prioritize | Force-rank all candidates; cut bottom items. If tied, ask "which one, if achieved, makes the others easier?" |
| Key result has no measurable baseline | Metric is not yet tracked | Spend 1-2 days instrumenting the metric before finalizing OKRs. Use a proxy metric if instrumentation takes longer. |
| Team OKRs don't ladder to company OKRs | Misalignment or team has competing priorities | Re-run Step 4 cascade session. Each team must map at least 1 KR to a company KR. |
| 100% of OKRs scored 1.0 at quarter-end | Targets were not ambitious enough | Next quarter, increase targets by 30-50%. Aspirational OKRs should hit 0.6-0.7 on average. [src1] |
| 100% of OKRs scored below 0.3 | Targets were unrealistic or external conditions changed | Retrospect on whether the objectives were wrong, or execution was blocked. Adjust scope for next quarter. |
| Check-ins abandoned after week 3 | Process fatigue or lack of leadership commitment | Simplify to async confidence scores only (1 number per KR). Leadership must model participation. [src6] |

## Cost Breakdown

<!-- Real cost analysis so agents can warn users before execution. -->

| Component | Free Tier | Paid Tier | At Scale (50+ users) |
|-----------|-----------|-----------|----------|
| OKR drafting & tracking | Google Sheets ($0) | Weekdone ($9/user/mo) | Lattice ($11/user/mo) |
| Check-in facilitation | Manual meeting ($0) | Weekdone auto-prompts ($0 extra) | Quantive automated ($0 extra) |
| Scoring & analytics | Manual spreadsheet ($0) | Built-in scoring ($0 extra) | Custom dashboards ($0 extra) |
| Training & coaching | Self-guided via books ($0-$30) | Weekdone coaching ($0 extra) | Consultant ($2K-5K/quarter) |
| **Total for 10-person team** | **$0-$30** | **$90-$110/month** | **$110+/month + optional consulting** |

## Anti-Patterns

### Wrong: Using OKRs as a To-Do List
Writing key results like "Launch feature X" or "Complete project Y." These are tasks, not outcomes. You can complete every task and still fail the objective if the tasks do not move the metric. [src2]

### Correct: Outcome-Oriented Key Results
Write KRs that describe the change you want to see: "Increase weekly active users from 500 to 1,200" — now the team chooses the best tasks to move that number.

### Wrong: Setting OKRs in Isolation
Each team writes OKRs alone in a room. Result: conflicting priorities, duplicated effort, and orphaned company objectives with no team ownership. [src3]

### Correct: Cross-Functional OKR Review
Teams draft OKRs independently, then present them to each other in a shared session. This surfaces dependencies, conflicts, and alignment gaps before the quarter starts.

### Wrong: Punishing Low OKR Scores
Tying OKR scores to bonuses or performance reviews. Result: everyone sandbagging targets to guarantee 1.0 scores. Innovation and ambition die. [src1]

### Correct: Celebrate Learning from Ambitious Misses
A 0.6-0.7 on an aspirational OKR is success. Reward the team for what they learned and achieved, not just the number. Use separate performance management systems.

### Wrong: Setting and Forgetting
Writing OKRs in week 1, then never looking at them until week 12. The quarter ends with surprised faces and meaningless scores. [src5]

### Correct: Weekly Confidence Scoring
Every owner rates their KR confidence (1-10) weekly. A drop from 8 to 5 in week 4 triggers early intervention — not a quarter-end postmortem.

## When This Matters

Use this recipe when a startup needs to establish a structured goal-setting rhythm for the first time, or when an existing OKR process has broken down and needs a reset. This is an execution recipe — it produces an actual OKR document and check-in cadence, not a strategy about whether to use OKRs. Requires clarity on company direction and current metric baselines as inputs.

## Related Units

- [North Star Metric Selection](/business/startup-metrics/north-star-metric-selection/2026) — defines the top-level metric that informs objective priorities
- [Startup KPI Dashboard Design](/business/startup-metrics/startup-kpi-dashboard-design/2026) — tracks OKR key results in real time
- [Startup Metrics Benchmarks 2026](/business/startup-metrics/startup-metrics-benchmarks-2026/2026) — industry benchmarks for validating key result targets
- [V2MOM Goal Setting](/business/startup-metrics/v2mom-goal-setting/2026) — Salesforce V2MOM as an alternative to OKRs