← All OKR examples

Company OKRs: real examples, explained

A company OKR holds up when it is few, memorable, honest about the baseline, and clear enough for teams to write their own goals against.

Company-level OKRs set the direction the teams write their own goals against. They earn their keep by being few, memorable and honest about the baseline. A company objective that tries to cover everything guides nothing.

The strongest company OKRs share a trait that is easy to miss: a team reading them can tell what to stop doing. If every existing project still fits comfortably under the new objective, it has not made a choice.

A leadership team reviewing company OKRs

Objective: Prove people want this before we scale it

  • Raise week-4 retention of new signups from 18% to 40%
  • Grow paying customers from 8 to 30
  • Reach 40% of users who would be very disappointed without the product, up from 22%

Level: Company Company type: Startup Company type: SaaS

Coach’s score ★★★★

Measurable ★★★★★

Outcome-based ★★★★★

Focused ★★★★

Niklas Olsson

Niklas Olsson · OKR coach

Overall strong, clear, and very ambitious, which is common with startups. Many times startups are exactly the kind of organisation that can really benefit from ambitious OKRs. With a lack of baselines, experts, and experience of what actually works, you can see results that double or triple the current level.

Number three is a fun one: reach 40% of users who would be very disappointed without the product. At the same time it needs some kind of measurability settled up front. Will this be measured at the end of the quarter with a survey to all customers, or is there a better metric for this satisfaction score?

Good questions

How many company OKRs should we set?

One to three objectives per cycle, and one is a respectable answer. Every additional company objective multiplies across the teams that align to it. Three focused objectives that every team can recite beat five that need the slide deck open.

Should company OKRs cascade down to teams?

Direction should travel down; the goals themselves should be written by the teams that own the work. A team that writes its own OKR against the company objective understands it and defends it at every check-in. A team handed a pre-cut slice of someone else's numbers executes it at half heart.

Now write yours

OKRnest gives your team the structure these examples are built on, and a weekly check-in habit that keeps them alive. Free for up to 3 users.