← Alla OKR-exempel

Product OKRs: real examples, explained

Great product OKRs are truly outcome focused, going beyond timelines and projects

OKRs are very easy to treat as project management tool and to start putting up project timelines as key results. Great Product teams manage to identify their true outcomes and target those instead, to let the team work on several parallel tracks to achieve the outcomes. Meeting lots of Product teams it becomes quite clear that some teams are strong in this regard while other teams have to work hard to identify what outcomes they are actually driving.

A product team's OKR overview in OKRnest

OKRs for product managers

The roles in a product team will impact both formats and content of OKRs. Where Product managers can bring in real outcomes to their key results, product owners many times have to identify process or more internal metrics.

Mål: Make the first week prove the product's worth

  • Raise week-one activation from 34% to 55%
  • Lift day-30 retention of new accounts from 61% to 72%
  • Cut steps to first key action from 9 to 4

Nivå: Team Team: Product Bolagstyp: SaaS Roll: Product manager

Measurable ★★★★★

Outcome-based ★★★★★

Focused ★★★★★

Niklas Olsson

Niklas Olsson · OKR-coach

This is a strong, measurable, and outcome-based product OKR. The feeling here though is that the team is trying to solve all their issues in one single OKR cycle. It takes on a little too much. When a team looks at an OKR like this and sees they are basically done, that they have covered all their workstreams with one OKR, it is a little too generic, a little too broad, a little too ambitious. They are measuring the right things, but from experience following teams like this, it is very seldom that you actually achieve all of this in one run. It might look like clear, slim focus because it is all about the onboarding process, but the onboarding process is a gigantic topic. It would be more believable, and easier to actually see a change from the work, if it was to make the first week prove the product's worth for a specific niche or kind of customer, or in a specific part of the solution.

There is a good mix here: one and two are clear outcome-focused, while number three is more of an activity, a to-do list item. But it puts up a clear ambition for the change. It is clearly measurable, can drive the right activities, and it is easy to see how number three drives future outcomes. It still works really well as a key result.

Mål: Make what we ship stick, not just ship more

  • Raise 30-day adoption of major releases from 12% to 20%
  • Grow weekly active use of the flagship feature from 18% to 26% of accounts

Nivå: Team Team: Product

Coachens poäng ★★★★★

Measurable ★★★★★

Outcome-based ★★★★★

Focused ★★★★★

Niklas Olsson

Niklas Olsson · OKR-coach

Some interesting measurability in this OKR, which is good, but there's also plenty of risk. The team could ship fewer major releases, or end up measuring every release by the same yardstick. Say a release is aimed entirely at a very thin customer segment, but that segment gets a lot of value from it. Not every major release will fit this picture of broad adoption.

Good intentions, but there are potential issues in what this will be optimised for once it goes into the work.

Bra frågor

Are shipped features ever good key results?

It is not uncommon for a timeline or project to take place as a key result, and it is not always wrong. It helps the team stay focused and to discuss what matters in weekly check-ins. If the project can have a 0-100% completion follow-up as well it becomes somewhat measurable and gives data for good discussions.

If the team however starts having lists of projects in the key results, OKRs have become a project management tool and is no longer about goals.

How do product OKRs relate to the roadmap?

A great roadmap is many times derived from business outcomes and goals and OKRs should drive those outcomes. It is not uncommon for OKRs not to mention a word about the roadmap, instead a 'launch new onboarding experience' becomes a 'lower first time usage churn from X to Y' or similar.

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.

Vi behandlar dina personuppgifter enligt vår integritetspolicy.