Organization OKRs

Company-level objectives and key results that guide strategic direction during a wave.

Last updated

Organization OKRs (Objectives and Key Results) are the strategic goals set at the wave level. They define what the entire organization is trying to achieve during the planning cycle.

What Are Organization OKRs?

Organization OKRs answer the question: "What does our company need to accomplish this quarter?" They provide direction for all teams and create alignment across the organization.

Each organization objective includes:

Component Purpose
Title Clear statement of what you're trying to achieve
Description Context about why this matters
Objective Type Roofshot or Moonshot classification
Key Results Measurable outcomes that define success

Objective Types

Roofshots

Roofshots are achievable stretch goals - ambitious but realistic targets you're confident you can hit.

Characteristics:

  • 80% or higher confidence of achievement
  • Based on proven capabilities
  • Stretches the organization without being unrealistic
  • Most objectives should be roofshots

Example:

Increase customer retention from 85% to 90%

Moonshots

Moonshots are ambitious goals that push boundaries. They represent transformational change.

Characteristics:

  • 50% or lower confidence of achievement
  • Requires innovation or breakthrough thinking
  • Failure still produces valuable progress
  • Limit to 1-2 per wave

Example:

Launch in three new international markets

A healthy wave has mostly roofshots with 1-2 moonshots to drive innovation.

Key Results

Key results are the measurable outcomes that define whether an objective is achieved.

Structure

Each key result includes:

Field Purpose
Title What you're measuring
Baseline Value Where you're starting from
Target Value Where you want to end up
Current Value Where you are now
Unit Type How progress is measured

Unit Types

Key results support various measurement types:

  • Number - Raw counts (users, features, deals)
  • Percentage - Rates and ratios
  • Currency - Revenue, cost savings
  • Time - Duration metrics
  • Boolean - Yes/no completion

Progress Calculation

Progress is calculated automatically:

Progress = ((Current - Baseline) / (Target - Baseline)) x 100

For descending metrics (where lower is better):

Progress = ((Baseline - Current) / (Baseline - Target)) x 100

Creating Organization Objectives

Who Can Create

Only organization administrators can create and edit organization objectives. This ensures strategic alignment and prevents scope creep.

When to Create

Organization objectives are created during the draft phase of a wave. Once the wave becomes active, objectives are locked.

Best Practices

Good objectives are:

  • Specific about what will change
  • Measurable through key results
  • Time-bound within the wave
  • Aligned to company strategy

Avoid:

  • "Improve the product" - Too vague
  • "Ship 50 features" - Output, not outcome
  • "Make customers happy" - Not measurable

Better:

  • "Reduce customer churn from 5% to 3%"
  • "Increase NPS from 45 to 60"
  • "Launch mobile app with 10,000 monthly active users"

How Teams Align

Organization objectives create a framework for team alignment:

  1. Organization sets 2-5 strategic objectives
  2. Teams choose which objective to support
  3. Teams create their own objectives aligned to the organization objective
  4. Teams explain their alignment rationale

This is a pull model - teams choose their alignment rather than having it assigned. This creates ownership and ensures teams work on what they believe matters.

Viewing Progress

Wave Dashboard

The wave dashboard shows:

  • All organization objectives with current progress
  • Key result status (baseline, current, target)
  • Team alignment distribution
  • Weekly sentiment trends

Progress Indicators

Status Meaning
Not Started No progress recorded
In Progress Work underway
At Risk Behind schedule or facing blockers
Completed Target achieved

Lifecycle

Organization objectives follow the wave lifecycle:

Draft Phase

  • Create and edit objectives freely
  • Add and modify key results
  • Set baseline values from current data

Active Phase

  • Objectives are locked
  • Update current values as progress happens
  • Track weekly sentiment from teams

Completed Phase

  • Review final outcomes
  • Calculate achievement percentages
  • Document learnings

Archived Phase

  • Historical reference
  • Hidden from active views

Limits and Configuration

Default Limits

  • Maximum objectives per wave: 2-5 (configurable)
  • Key results per objective: No hard limit, but 3-5 recommended

Why Limits?

Research shows that focus drives results. Too many objectives dilute effort and reduce achievement rates. Organizations with 2-3 focused objectives consistently outperform those with 5+.

Integration with Other Features

Pulse Check

Teams vote on objective status weekly via Pulse Check using the Red/Amber/Green system. This provides early warning when objectives are at risk.

Team Objectives

Team objectives inherit context from organization objectives but define team-specific contributions. See Team OKRs for details.

Incentives

Waves can optionally include incentive configuration tied to organization objective achievement.


Next steps: During an active wave, view organization objectives and their progress from the Wave dashboard.