← Alla OKR-exempel

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

OKR-exempel för SaaS på Company-nivå

Mål: Make the product something customers grow into, not out of

  • Lift net revenue retention from 96% to 110%
  • Grow accounts actively using 3 or more modules from 22% to 40%
  • Halve monthly logo churn from 2.4% to 1.2%

Nivå: Company Bolagstyp: SaaS

Coachens poäng ★★★★★

Measurable ★★★★★

Outcome-based ★★★★★

Focused ★★★★★

Niklas Olsson

Niklas Olsson · OKR-coach

I imagine this as a company-wide rallying cry for the entire organisation. This is a strategic OKR. It's extremely ambitious, and it's very, very clear for the organisation. I think this can work really well if there is not another OKR that says new sales must double as well, if this is clearly the focus of the organisation for the year. It's strong, and it attacks a strategic focus from many directions.

The quality of this OKR depends a lot on what environment it is in. If it's surrounded by three equally aggressive OKRs in completely different areas, then it's just a company that wants to do it all. If this really clearly signals focus for the organisation (maybe it's just this one and one about building for innovation or team strength), then I think it can work really well.

Mål: Prove the DACH market can carry our next stage of growth

  • Grow annual recurring revenue from €1.2M to €1.6M
  • Raise the share of new ARR from the DACH region from 5% to 15%
  • Shorten CAC payback from 19 to 15 months

Nivå: Company Bolagstyp: SaaS Bolagstyp: Startup

Coachens poäng ★★★★★

Measurable ★★★★★

Outcome-based ★★★★★

Focused ★★★★★

Niklas Olsson

Niklas Olsson · OKR-coach

Overall, this is a strong OKR, but it's quite sales- or finance-oriented, leaning almost a little too much toward a budget. The only strategy here is a focus on a specific geography. What that often means is that it's directed at a specific team, maybe not a rallying cry for the entire organisation. When these work, what I usually see is the sales effort, together with marketing, needing to adapt to a new language, for example. Product needs to adapt to a new market, or maybe legal even has to start work to support the sales effort in Germany. It is possible to rally the entire organisation around something as simple as a new geography with financial metrics like this, but this example does not quite show that yet.

Overall, this kind of OKR works well. I would say all three hold up here, including shortening payback. For clarity, if this is a strategic OKR for the entire organisation, it would be nice to write out customer acquisition cost, but it's also hard to understand how that fits into the objective. Why do we have a CAC target on this one? Maybe we need to clarify the objective, then talk about how DACH can sustain the next stage of growth. For example, sales in this new market need to hit a specific level of profitability. For the right organisation in the right context, this hits the marks.

OKR-exempel för Startup på Company-nivå

Mål: 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%

Nivå: Company Bolagstyp: Startup Bolagstyp: SaaS

Coachens poäng ★★★★★

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?

Mål: Build the sales engine our next stage needs

  • Close 4 deals without a founder in the room, up from 0
  • Win 30% of new deals following the documented 30-day playbook, up from 0%

Nivå: Company Bolagstyp: Startup

Coachens poäng ★★★★★

Measurable ★★★★★

Outcome-based ★★★★★

Focused ★★★★★

Niklas Olsson

Niklas Olsson · OKR-coach

This OKR has its heart in the right place, and it's clear what it wants to achieve. I would say the key results are maybe a little limiting, or uncertain about whether they're hitting the right thing here. Would this potentially force the founder out of the room in important sales processes? Is that really what the team wants to achieve? And is playbook adherence really the road to building a sales engine without the founder involved?

There are a couple of thoughts in here that might have the effect that the team avoids taking support from the founder, or avoids taking the decisions needed to close the deal because they're adhering to a playbook. It risks having a problematic effect on the team, even though its intention is clear. I think it's more about reformulating and finding stronger key results for this one.

Bra frågor

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.

Skriv era egna nu

OKRnest ger ditt team strukturen som exemplen bygger på, och en veckovis check-in-vana som håller dem vid liv. Gratis för upp till 3 användare.