OKRs and Goals

OKR stands for Objectives and Key Results. The method helps teams pick a few important goals and measure progress with clear numbers. Many product organizations use OKRs to keep daily work tied to company direction.

Imagine a family planning a long road trip. The objective is "reach the coast and enjoy the journey." Key results are the checkpoints: "arrive by Friday evening," "stop at three scenic spots," "stay under the fuel budget." The objective inspires, and the checkpoints prove progress.

The Two Parts

OBJECTIVE        A short, inspiring statement of what you want
                 "Make new users feel at home quickly"

KEY RESULTS      2 to 4 measurable outcomes that prove progress
                 KR1  Raise day-7 retention from 25% to 35%
                 KR2  Cut setup time from 8 minutes to 4 minutes
                 KR3  Lift onboarding survey score from 3.6 to 4.2

Write a Strong Objective

• Use plain, energetic words that anyone understands
• Describe the change you want, not a list of tasks
• Keep it ambitious yet realistic for one quarter
• Limit each team to three objectives at most

Write Strong Key Results

Each key result states a number that moves from a starting value to a target value. Anyone should be able to check the number and agree whether the team succeeded.

WEAK KEY RESULT                    STRONG KEY RESULT
─────────────────────────────────────────────────────────────
Improve onboarding          →      Cut setup time from 8 to 4 minutes
Launch new search           →      Raise search success rate from 60% to 80%
Talk to customers           →      Learn from 20 interviews; ship 2 changes

Key results measure outcomes, such as changes in customer behavior. They avoid listing outputs, such as "launch feature X." A launched feature that nobody uses achieves nothing.

Align Goals Across Levels

COMPANY OBJECTIVE
Become the easiest tool for small businesses
          │
          ├── PRODUCT TEAM OBJECTIVE
          │   Make new users feel at home quickly
          │        │
          │        └── Key results on retention, setup time, satisfaction
          │
          └── SUPPORT TEAM OBJECTIVE
              Solve customer problems on the first reply

Alignment does not mean copying. Each team chooses objectives that support the layer above in its own way.

The OKR Rhythm

START OF QUARTER    Draft and agree on OKRs
        ↓
EVERY WEEK          Update progress and note risks
        ↓
MID-QUARTER         Review honestly and adjust plans
        ↓
END OF QUARTER      Score results and capture lessons
        ↓
NEW QUARTER         Set fresh OKRs using those lessons

Score Without Fear

Teams often score key results from zero to one. A score near 0.7 on an ambitious target counts as a strong result. Perfect scores every time may signal goals that feel too easy. Treat the score as a learning signal. Avoid linking OKR scores directly to pay or personal performance reviews, since fear leads people to set safe, small targets.

OKRs and the Roadmap

OKRs state the destination. The roadmap shows the routes. When a roadmap item does not support any key result, question its place. Key results without a roadmap item need planned work that can move them.

Common Mistakes

• Setting too many objectives
• Writing key results as task lists
• Setting goals once and forgetting them until quarter end
• Choosing numbers nobody can measure
• Punishing teams who miss ambitious targets

A Worked Quarter

Consider a product team at a small accounting app. In January, the team notices that new users abandon setup. The objective reads "Help new users succeed in their first week." Three key results follow: raise week-one activation from 30 to 45 percent, cut average setup time from ten minutes to five, and lift the new-user satisfaction score from 3.5 to 4.2.

Each week, the product manager updates the numbers and notes obstacles. By week six, setup time drops to six minutes, yet activation barely moves. The team interviews five struggling users and discovers confusion about importing old data. A guided import tool joins the plan. At quarter end, activation reaches 41 percent, setup time hits five minutes, and satisfaction reaches 4.1. The team scores the quarter around 0.8, records the lesson about data import, and starts the following quarter with a fresh objective.

Share Goals Openly

Publish every team's OKRs where everyone can read them. Open goals reveal overlaps and invite early offers of help. Colleagues in other teams often hold the missing piece.

Key Takeaways

OKRs combine an inspiring objective with measurable key results. Keep the set small, measure outcomes, and review progress every week. Use scores to learn, and link every roadmap item back to a goal.