OKR Basics: What Objectives and Key Results Actually Are
A beginner's guide to OKR basics — what an Objective is, what a Key Result is, how they differ from a to-do list, and the cadence most teams use.
In this article
If you're new to OKRs, skip the long framework history — here's the short version of what the two halves of the name actually mean, and the handful of rules that keep teams from writing them wrong.
What Is an Objective?
An Objective is a qualitative, ambitious statement of where you want to go. It answers "what do we want to achieve," not "how much" or "by when." A good objective is short enough to remember without looking it up, and inspiring enough that people want to work toward it.
- Good: "Become the fastest-growing OKR tool for small teams."
- Not an objective (it's a key result): "Grow signups by 30%."
What Is a Key Result?
A Key Result is how you know whether you reached the objective. It's a number — a measurable outcome with a baseline and a target, not a task. If you can't score it from 0–100% without a judgment call, it isn't a key result yet.
- Good: "Increase weekly active teams from 500 to 800."
- Not a key result (it's a task): "Launch the new onboarding flow."
Every objective typically has 2–4 key results. If an objective has one key result, it's probably actually a key result itself; if it has eight, it's probably two or three objectives merged together.
Objectives vs. Key Results, Side by Side
| Objective | Key Result | |
|---|---|---|
| Type | Qualitative | Quantitative |
| Answers | What do we want? | How do we know we got there? |
| Example | Delight new customers | Raise onboarding completion from 60% to 85% |
| Changes how often | Rarely within a cycle | Tracked every check-in |
What Cadence Do Teams Use?
Quarterly is the most common cycle length — long enough to make real progress, short enough to course-correct before a bad target does damage. Some fast-moving product teams run monthly cycles; some slower functions (finance, legal) run on a half-year cycle instead.
The Most Common Beginner Mistakes
- Writing a task list and calling it key results. "Ship feature X" is an activity, not an outcome — ask "what happens because we shipped it?"
- Setting too many objectives. Three to five per team is a reasonable ceiling; more than that means nothing is actually prioritized.
- No baseline. "Increase retention" isn't measurable without a starting number. Always write key results as from X to Y.
- Scoring every OKR at 100%. If everything hits 1.0 every cycle, the targets weren't ambitious — aim for an average score around 0.6–0.7.
Next Step: Actually Implementing Them
Once the basics click, the harder part is making OKRs stick past one quarter — deciding your cadence, cascading across teams, and running check-ins. That's covered step by step in how to implement OKRs.
Want to see what real objectives and key results look like for your function or industry? Browse the OKR examples hub.
Keep reading
16 Reasons for Unbalanced Progress in Your OKR Strategy
Discover the key causes of unbalanced progress in your OKR strategy and explore practical solutions. This comprehensive guide underscores the importance of effective leadership, team cohesion, target setting, and review processes to drive alignment and growth.
12 Compelling Reasons Why OKR Software is Essential for Organizational Success
Discover the 12 key reasons why OKR software (Objectives and Key Results) is essential for organizational success. Learn how it provides direction, fosters alignment, enhances accountability, and drives innovation while promoting employee engagement through a streamlined goal-setting framework.
10 Key Qualities That Distinguish Leaders from Managers for Effective OKR Management
Explore the key qualities that differentiate leaders from managers to enhance team performance and promote effective OKR management practices.