OKR examples by department turn a company's top objectives into measurable goals each team can own. Below are 200+ real Objectives and Key Results for the company level plus Engineering, Sales, Customer Success, Marketing and HR — organized by seniority so you can copy the ones at your level. In Sears Holding's landmark rollout, associates using OKRs lifted average sales-per-hour by 8.5%.
Every example follows the same shape: one qualitative Objective (the direction) plus two to five quantitative Key Results (the proof). Steal them, swap in your own baselines and targets, and pressure-test each one against the diagnostic and the good-vs-bad comparison further down.
What makes a good OKR example (before you copy anything)
A useful example is more than a nicely worded sentence. Three rules separate OKRs that move a business from ones that just decorate a slide:
- The Objective is an outcome, not a task. "Launch the mobile app" is a project. "Make mobile the primary way customers buy from us" is an objective.
- Every Key Result is a number with a baseline and a target. "Improve onboarding" is a wish; "cut time-to-first-value from 14 days to 5" is a Key Result.
- OKRs are stretched, not sandbagged. Google's own guidance is to size them so roughly 60–70% achievement counts as success — hitting 100% every quarter means you aimed too low, per Google re:Work's OKR guide.
Company-level OKR examples
Company OKRs sit at the top of the tree. Everything else cascades from them, so they should be few, cross-functional, and tied to the year's biggest bets — usually revenue, market position, product, and financial health. Keep it to three to five for the whole organization.
| Objective | Key Results |
|---|---|
| Become the default choice in our core segment | Grow ARR from €12M to €18M; lift win rate against our top competitor from 34% to 45%; reach 55 NPS across the customer base; land 3 reference logos in the enterprise tier |
| Turn the product into our strongest growth engine | Move 40% of new revenue to product-led signups; raise activation rate from 28% to 45%; ship 2 of the top-3 customer-requested capabilities; cut median time-to-value from 21 to 10 days |
| Build a financially durable business | Improve gross margin from 68% to 74%; extend runway from 14 to 24 months; bring net revenue retention to 115%; reduce CAC payback from 16 to 11 months |
| Make the company a place top talent joins and stays | Fill 90% of leadership roles internally; raise regretted attrition ceiling to under 6%; reach eNPS of 40; close every open critical role within 45 days |
Engineering team OKR examples
Engineering OKRs work best when they measure outcomes users feel — reliability, speed, security — rather than raw output like story points. Below are examples split by seniority, from individual contributor to director.
Individual contributor (engineer)
| Objective | Key Results |
|---|---|
| Ship reliable code that rarely comes back | Keep change-failure rate under 8%; resolve 95% of assigned PR reviews within one working day; reduce personally-owned bugs escaping to production from 6 to 2 per quarter |
| Grow into a stronger, faster contributor | Complete 2 skill certifications relevant to the roadmap; cut average cycle time on my tickets from 4.5 to 2.5 days; pair with a teammate on 4 features outside my usual area |
Engineering manager
| Objective | Key Results |
|---|---|
| Make the team ship faster without breaking things | Raise deployment frequency from weekly to daily; cut lead time for changes from 6 days to 2; hold change-failure rate under 10%; keep mean-time-to-restore under 1 hour |
| Build a team that scales | Onboard 3 new engineers to first production ship within 3 weeks; reach 90% documentation coverage on owned services; lift team eNPS from 22 to 40 |
Director / VP of Engineering
| Objective | Key Results |
|---|---|
| Deliver a platform the business can bet on | Hit 99.95% uptime across critical services; close 100% of high-severity security findings within SLA; reduce infrastructure cost per active user by 20% |
| Turn engineering into a talent magnet | Cut senior-engineer time-to-hire from 60 to 40 days; keep regretted attrition under 5%; run a skills matrix covering 100% of the org so gaps are visible before they hurt delivery |
If your Engineering objectives lean on closing capability gaps, tie the Key Results to an explicit skills framework rather than gut feel — our guide to skill management shows how to make those gaps measurable.
Sales department OKR examples
Sales is the easiest function to over-measure on lagging numbers alone. The strongest sales OKRs pair a revenue outcome with the leading behaviors that produce it — pipeline coverage, conversion, sales-cycle length.
Account executive
| Objective | Key Results |
|---|---|
| Consistently beat quota with healthy deals | Close €1.2M in new ARR; keep discount average under 12%; maintain 3.5x pipeline coverage; move win rate from 22% to 30% |
| Sell more strategically, not just harder | Run multi-threaded deals (3+ contacts) on 80% of opportunities over €50k; cut average sales cycle from 74 to 55 days |
Sales manager
| Objective | Key Results |
|---|---|
| Build a predictable, repeatable pipeline | Reach 4x qualified pipeline coverage every month; lift team quota attainment from 68% to 85%; reduce ramp time for new reps from 5 to 3 months |
| Raise the floor on deal quality | Cut slipped deals from 30% to 15%; grow average deal size 20%; reach 90% CRM hygiene on required fields |
VP of Sales / CRO
| Objective | Key Results |
|---|---|
| Turn sales into a scalable growth engine | Grow net-new ARR 45% year over year; improve forecast accuracy to within 10%; bring CAC payback from 16 to 11 months; hit 115% net revenue retention with the CS team |
Customer Success OKR examples
Customer Success OKRs should be built around retention and expansion, not activity. Ticket counts and call volume are inputs; the outcomes that matter are whether customers renew, grow, and would recommend you. These are the sharpest, most specific examples in this guide — because retention is where vague goals do the most damage.
Customer success manager (CSM)
| Objective | Key Results |
|---|---|
| Make my accounts measurably more successful | Reach 95% gross retention across my book; drive €300k in expansion ARR; complete quarterly business reviews with 100% of accounts over €25k; lift portfolio NPS from 41 to 55 |
| Catch churn risk before it becomes a cancellation | Flag every at-risk account 60 days before renewal; get 80% of red-health accounts back to green within a quarter; keep product adoption above 70% of licensed seats |
CS manager / team lead
| Objective | Key Results |
|---|---|
| Turn onboarding into the reason customers stay | Cut time-to-first-value from 21 to 10 days; reach 90% onboarding completion within 30 days; lift 90-day activation from 55% to 75% |
| Build a retention machine, not a firefighting team | Improve net revenue retention from 104% to 115%; cut logo churn from 9% to 5%; move 30% of support tickets to self-service deflection |
VP of Customer Success
| Objective | Key Results |
|---|---|
| Make retention a company-wide advantage | Reach 118% net revenue retention; keep gross retention above 92%; turn 40 customers into referenceable advocates; tie 25% of new pipeline to customer referrals |
Marketing department OKR examples
Marketing OKRs go wrong when they stop at vanity metrics — impressions, follower counts, MQL volume. Anchor them to pipeline and revenue influence instead, and keep brand goals qualitative-but-measurable (share of voice, branded search).
Marketing specialist / IC
| Objective | Key Results |
|---|---|
| Turn content into a pipeline source, not a cost center | Grow organic sessions from 40k to 65k per month; lift blog-to-lead conversion from 1.8% to 3%; publish 12 pieces that each rank on page one for a target keyword |
Marketing manager
| Objective | Key Results |
|---|---|
| Deliver pipeline the sales team actually wants | Generate €4M in marketing-sourced pipeline; raise MQL-to-SQL conversion from 18% to 30%; cut cost per SQL by 25%; grow email-driven revenue 40% |
| Build a brand people search for by name | Increase branded search volume 35%; grow share of voice in our category from 12% to 20%; reach 15k newsletter subscribers with 45% open rate |
Head of Marketing / CMO
| Objective | Key Results |
|---|---|
| Make marketing a measurable revenue engine | Source 45% of total pipeline; improve marketing-influenced win rate to 38%; hold blended CAC flat while doubling lead volume; launch 2 campaigns that each drive €1M+ in influenced revenue |
HR and People team OKR examples
People OKRs are where "engagement" and "culture" either become measurable or stay as slideware. Tie them to retention, hiring speed, internal mobility, and capability — outcomes leadership can act on. This is also where OKRs collide with real-world rollout constraints most, especially in Germany, Austria and Switzerland (see the callout below).
HR / People specialist
| Objective | Key Results |
|---|---|
| Make hiring fast and fair | Cut time-to-hire from 42 to 30 days; reach 85% offer-acceptance rate; ensure every open role has a structured, scorecard-based interview loop; keep candidate NPS above 40 |
HR manager / People lead
| Objective | Key Results |
|---|---|
| Keep the people we can't afford to lose | Cut regretted attrition from 11% to 6%; lift eNPS from 24 to 42; complete stay interviews with 100% of high performers; reach 90% completion of manager 1:1s |
| Grow talent from within | Fill 40% of open roles internally; give 100% of employees a documented development plan; run a skills matrix across the org so capability gaps are visible |
Head of People / CHRO
| Objective | Key Results |
|---|---|
| Build a workforce ready for next year's strategy | Reach 75% internal fill rate for leadership roles; close the top-3 strategic skill gaps to under 15%; raise engagement to 80% favorable; keep regretted attrition under 6% |
If OKRs are the front end of a broader performance and development system, they need a platform that connects goals to skills, reviews and internal mobility — our talent-management software comparison for DACH walks through the buying criteria, including GDPR and works-council considerations.
Cascading OKRs and review rhythms
Cascading does not mean copying the CEO's OKRs downward. It means each level answers one question: "What can my team own that helps the level above hit theirs?" Company OKRs set direction; department OKRs pick the lever that team controls; individual OKRs make it concrete.
Two practical rules keep this from turning into a spreadsheet ritual:
- How many OKRs per team? Keep it to 1–3 Objectives per team per quarter, each with 2–5 Key Results — the consensus across practitioner sources including John Doerr's What Matters. More than that and focus dissolves.
- Run a weekly check-in and a quarterly grade. Weekly: a 15-minute confidence check on each Key Result. Quarterly: score 0.0–1.0 and decide keep, drop, or carry over. The check-in cadence is what makes OKRs live, not the planning offsite.
The weakest link is almost always the weekly check-in, because it competes with everything else on a Monday. Some teams use an AI coworker such as sprad's Atlas to nudge owners for their confidence updates and surface Key Results that have gone quiet — light automation so the rhythm survives a busy quarter.
Good OKR vs. bad OKR: a quick before/after
Most weak OKRs share the same three faults: the Objective is a task, the Key Result has no number, or the target is a safe layup. Use this comparison to self-diagnose before you commit a set.
| Bad OKR (why it fails) | Good OKR (fixed) |
|---|---|
| "Improve customer satisfaction" (no number, no target) | Objective: Make customers actively recommend us. KR: Lift NPS from 41 to 55; cut first-response time from 6h to 2h |
| "Launch the new website" (a task disguised as a goal) | Objective: Make the site convert. KR: Raise visitor-to-lead conversion from 1.8% to 3.2%; cut bounce rate from 62% to 45% |
| "Hit €1M revenue" (the target we'd hit anyway) | Objective: Break into the enterprise segment. KR: Close 5 deals over €100k; reach 3x pipeline coverage in enterprise |
| "Do 100 sales calls" (activity, not outcome) | Objective: Fill a healthier pipeline. KR: Book 25 qualified meetings; convert 30% to opportunities |
Turning these examples into your own OKRs
Pick the two or three objectives closest to your team's real priorities this quarter. Replace every generic number with your own baseline and a genuine stretch target — the example's value is the shape, not the figure. Then run them through the good-vs-bad table, confirm each Key Result is a measurable outcome, and lock the weekly check-in before the quarter starts. If OKRs are part of a wider performance and skills strategy, see how goals connect to reviews and development in our guide to choosing performance-management software.
Frequently asked questions
How many OKRs should a team have?
Aim for 1–3 Objectives per team per quarter, each with 2–5 Key Results. Fewer objectives mean sharper focus; more than three and teams spread thin and hit none. Individuals typically carry one or two objectives tied to their team's set.
What is the 70% rule in OKRs?
OKRs are deliberately set as stretch goals, so achieving roughly 60–70% is considered success. Consistently scoring 100% is a signal the targets were too easy, per Google re:Work's OKR guidance. A small set of "committed" OKRs (things that must ship) are the exception and are expected to hit 100%.
What is the difference between company and department OKRs?
Company OKRs set the whole organization's direction for the year and are cross-functional. Department OKRs pick the specific lever a single team controls to help hit the company set. Individual OKRs make a person's contribution to the department goal concrete.
How often should you review OKRs?
Weekly for a short confidence check on each Key Result, and once per quarter for a full grade (0.0–1.0) plus a decision to keep, drop, or carry over. The weekly cadence is what keeps OKRs from becoming a document nobody opens.
Should OKRs be tied to compensation?
Most OKR practitioners advise keeping them separate from bonuses. Tie stretch goals to pay and people sandbag their targets, which defeats the purpose. In Germany, Austria and Switzerland there is also a legal dimension: linking goal attainment to pay can trigger works-council co-determination (see the DACH note in the HR section).
Jürgen Ulbrich
Jürgen Ulbrich has more than a decade of experience in developing and leading high-performing teams and companies. As an expert in employee referral programs as well as feedback and performance processes, Jürgen has helped over 100 organizations optimize their talent acquisition and development strategies.
