OKR Examples
Five OKR examples spanning marketing, engineering, sales, HR, and product management. Each example includes a complete Objective with 3 to 4 Key Results, baseline and target values, and editorial commentary on what makes the OKR effective and what pitfall it avoids. These are modeled on real team OKRs, not textbook abstractions.
When You Would Build This
A mid sized SaaS company (200 employees, 12 teams) is entering its third quarter of using OKRs. Each department sets 2 to 3 team level Objectives aligned to company priorities. The company level Objective for this quarter is “Accelerate growth while improving unit economics.” The following team OKRs show how five different functions translate that company direction into measurable goals specific to their work.
What Makes These Examples Useful
Reading about OKR theory is easy. Writing your first real OKR is hard. The gap between “set an aspirational Objective with measurable Key Results” and actually producing one for your Q3 planning meeting is where most teams stall.
These five examples cover different functions, team sizes, and goal types. Each one follows the same format: a qualitative Objective, 3 to 4 measurable Key Results with baselines and targets, and a brief commentary explaining why the OKR works and what common mistake it avoids.
Use them as starting points. Copy the structure, swap in your own metrics and targets, and adjust the ambition level to match your team’s maturity with OKRs. First time OKR teams should aim for targets they have a 70% chance of hitting. Experienced OKR teams should aim for targets they have a 50% chance of hitting.
Adapting These Examples to Your Team
The Objectives in these examples are intentionally generic enough to translate across organizations, but the Key Results are specific. That specificity is the point. When you adapt an example for your team, keep the Objective’s qualitative spirit but rewrite every Key Result with your own metrics, your own baselines, and your own targets.
Two common adaptation mistakes to avoid. First, do not copy Key Results without knowing your baseline. “Increase retention from 85% to 92%” only works if your current retention is actually 85%. Second, do not water down the Objective to match your Key Results. If your Key Results feel easy, make them harder rather than softening the Objective to match.
Marketing Team OKR
Objective: Build a content engine that generates qualified pipeline without paid spend.
| Key Result | Baseline | Target | Q3 Score |
|---|---|---|---|
| Marketing qualified leads from organic content | 120/mo | 300/mo | 0.7 |
| Organic traffic to product pages | 18,000/mo | 40,000/mo | 0.6 |
| Content influenced pipeline value | $400K | $1.2M | 0.8 |
Why this works: The Objective is qualitative (“content engine” is aspirational, not measurable). All three Key Results measure outcomes (leads, traffic, pipeline), not activities (articles published). The 0.7 average score indicates healthy ambition.
Engineering Team OKR
Objective: Ship features faster without increasing the defect rate.
| Key Result | Baseline | Target | Q3 Score |
|---|---|---|---|
| Average cycle time from commit to production | 8 days | 3 days | 0.6 |
| Production incidents per release | 2.1 | 0.5 or fewer | 0.7 |
| Automated test coverage on critical paths | 62% | 90% | 0.8 |
Why this works: The Objective contains a built in tension (speed vs. quality) that prevents gaming. You cannot hit the cycle time target by skipping tests because the incident rate and coverage targets would suffer. This kind of balanced OKR produces real improvement instead of metric manipulation.
Sales Team OKR
Objective: Win larger deals with shorter sales cycles.
| Key Result | Baseline | Target | Q3 Score |
|---|---|---|---|
| Average deal size (new business) | $28K ARR | $45K ARR | 0.5 |
| Average sales cycle length | 64 days | 45 days | 0.7 |
| Win rate on deals over $50K | 18% | 30% | 0.6 |
| Expansion revenue from existing accounts | $180K/qtr | $350K/qtr | 0.9 |
Why this works: The 0.5 score on deal size shows this was a genuine stretch target. A team consistently scoring 0.9 or 1.0 on every Key Result is sandbagging. The expansion revenue score of 0.9 suggests that was the easier lever, which informs next quarter’s target setting.
HR Team OKR
Objective: Make the first 90 days so good that new hires become recruiters.
| Key Result | Baseline | Target | Q3 Score |
|---|---|---|---|
| New hire 90 day retention rate | 82% | 95% | 0.7 |
| Average onboarding satisfaction score (survey) | 3.4/5 | 4.5/5 | 0.8 |
| Time to first meaningful contribution | 6 weeks | 3 weeks | 0.6 |
Why this works: The Objective is memorable and creates an emotional target the team can rally around. “Make new hires become recruiters” is more motivating than “improve onboarding metrics.” The Key Results ground that aspiration in verifiable numbers.
Product Team OKR
Objective: Become the default choice for teams migrating from spreadsheets.
| Key Result | Baseline | Target | Q3 Score |
|---|---|---|---|
| Trial to paid conversion from “spreadsheet migration” segment | 8% | 18% | 0.6 |
| Data import completion rate | 34% | 75% | 0.7 |
| Time from signup to first shared project | 4.2 days | 1 day | 0.5 |
Why this works: This OKR targets a specific user segment (spreadsheet migrators) rather than “all users.” Narrow focus produces actionable insights. If the import completion rate jumps to 75% but conversion only hits 12%, the team knows the bottleneck is not import friction but something later in the journey.
What Makes This Example Work
These five OKRs share four qualities worth copying. First, every Objective is qualitative and memorable. None of them contain numbers. Second, every Key Result includes a baseline, which prevents the common mistake of setting targets without knowing your starting point. Third, the scores range from 0.5 to 0.9, which indicates genuine ambition. A set of OKRs where every score is 0.9 or above signals targets that were too easy. Fourth, each OKR set contains at least one Key Result that creates tension with another (speed vs. quality, volume vs. deal size), which prevents teams from gaming a single metric at the expense of others.
Common Questions About OKR Examples
How do I know if my OKR is ambitious enough?
If you are confident you will hit every Key Result, the targets are too conservative. A well calibrated OKR set should feel achievable with strong execution but uncertain without it. Aim for targets where your team has roughly a 50% to 70% chance of hitting them. Scores of 0.6 to 0.8 at quarter end indicate the right ambition level.
Should every team use the same OKR format?
The structure should be consistent (Objective plus 3 to 5 Key Results with baselines and targets) so teams can compare and align. The content varies by function. A sales team measures pipeline and deal size. An engineering team measures cycle time and defect rates. Standardize the format, not the metrics.
What if a Key Result becomes irrelevant mid quarter?
Mark it as deprecated in your tracker and add a brief note explaining why. Do not delete it, because the history is useful during the retrospective. If the change is significant enough, add a replacement Key Result. Avoid swapping Key Results frequently, though. That usually signals the Objective itself was not well defined.