Skip to main content

Demystifying OKR Scoring

[PLACEHOLDER]
Image

You have probably read that one of the many good things about OKRs is that it provides structure and clarity to work towards common goals. It helps connect company, teams and individuals’ objectives to measurable results.

 

Photo by Garreth Brown via Pexels

In a previous Beolle article, Herak wrote about HOSKR and OKRs.

In this iteration we will focus on the OKR scoring.

Measuring the “How”

The KRs in OKRs are the Key Results. With them we measure the progress towards the Objectives we have set. So how do we score them in a way that makes sense, and measure the success?

Few “gotchas” before we start

  1. Grades are an indication where you're going.
  2. In OKRs, scoring between .6 to .7 is your target. Scores between .8 and 1.0 are rare, meaning they are not the usual. If you find yourself completing all your OKRs within this range then something is not correct, for example, your Objectives are not Ambitious enough, meaning you always knew you (or your company or your team) were going to achieve it without much effort.
  3. Low grading isn't to be punished.
  4. Scores matter less than the process. If you are taking too long during the scoring gathering, preventing you, or the team, from “doing”, then reconsider and correct the approach. 
  5. Company-wide scoring enforces the commitment.
  6. The scoring is a guide of what to keep doing, what to change, what not to keep doing. 
  7. The sweet spot for the amount of KRs within the same Objective is three (3). Having said that, you could have more, if you think that makes sense to your OKR.
  8. Focus on the results when scoring, meaning on fulfilling the outcome. Needs to be clear why you are giving that grade. Be ready to explain it. 
  9. Always welcome your team members’ opinions.
  10. Publicly grade organizational OKRs. 
pexels-berk-ozdemir-displayed-in-Beolle-Blog

How to score the OKRs?

  1. Have regular meetings to check how the OKRs are doing.
  2. Place the grading. Where 0 means no progress, and 1.0 means complete.
  3. Calculate a score for the objective, which is an average from the gradings. Tip: My personal preference is keeping it simple by avoiding different weights. Keeping an equal weight for all will simplify the use of the tool and the reporting. 
  4. Once calculated, the team needs to review the scoring together. Chat about challenges and blockers getting in the way to meet the Objectives. This allows them to identify the areas of improvement, determining if they stay course, or if there are opportunities to pivot. 
  5. Assign to work, teams and individuals to execute, and the cycle begins again.

There are a few ways to work on the scoring. I will stick with the traditional grading scale approach.

You want to review your OKRs frequently. With proper tools, you can log your process as close to real-time as possible. Tracking often will help with accuracy.  

In the traditional grading:

  1. You score your KRs in a scale of 0.1 to 1.0
  2. Leverage colours, representing rate of success.
    1. Green is from 0.7 to 1.0.  This is for a status of completed/delivered/DONE. 
    2. Yellow is from 0.4 to 0.6. This is for “progress has been made, but we felt short”
    3. Red is from 0 to 0.3. This is for “we have failed to make significant progress”

0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1.0


Ideally, OKR scores fall between 0.6 to 0.7 (60 to 70 percent). If scoring below 0.6, your team is underperforming. If consistently scoring above 0.7 or completing 100 percent of the results, your goals might be insufficiently ambitious

- Photo by Andrea Piacquadio


As an example, let us say you want to determine the Monthly objective score from Obj1, that has 3 KRs.
Obj1 score = (KR1 + KR2 + …+ KRn-1 + KRn)/Amount of KRs


Excel - OKR example.



What about tools?

Here are some examples:

Microsoft Excel Sheet

SmartSheets have good templates set for OKRs.

Trello. Leveraging cards and the waterfall chart.

Hive.

Note from the author

As a SAFe certified, and a person that enjoys the Scaled Agile Framework, it is always great to revisit the SAFe material that presents the Strategic Themes that connects the enterprise strategy to the portfolio vision. In there you will also find the relationship between Value Stream KPIs and the Strategic Themes.
Why this is relevant to the topic in this article is because the two (2) frameworks are linked together, complimenting each other, as OKRs are directly or indirectly related to the KPIs (See the image below).
If you want to read about this connection, then follow the value stream kpis link.  

Value stream KPIs are derived from strategic themes and local concerns


Trending posts

Steer for a talent transformation strategy (and avoiding AI fatigue)

 There was a debate on whether to feature the term “AI” in the title of this article. Honestly, a key motivation for pursuing the research that led to this post was sparked by the widespread excitement about AI appearing constantly in our LinkedIn feed, to the point of feeling the fatigue, and even a bit disappointed in the algorithm of this, and the others, social media and content curated apps.  We soon discovered that there is an entire concept called "AI fatigue", not exactly how we were feeling it, but more about the mixed emotions people in the workforce have regarding the use of AI tools. Photo by Mart Production via Pexels (background updated with AI and Adobe  tech) From micro blog posts to video podcasts, lately, most of the tech content we encounter revolves around AI. They often sound or read very similar, usually mentioning the same few top providers. The articles (and social posts... at least the popular ones with paid-campaigns behind it) tend to focus less...
Read more

Assembling MLOps practice - part 2

 Part I of this series, published in May, discussed the definition of MLOps and outlined the requirements for implementing this practice within an organisation. It also addressed some of the roles necessary within the team to support MLOps. Lego Alike data assembly - Generated with Gemini   This time, we move forward by exploring part of the technical stack that could be an option for implementing MLOps.  Before proceeding, below is a CTA to the first part of the article for reference. Assembling an MLOps Practice - Part 1 ML components are key parts of the ecosystem, supporting the solutions provided to clients. As a result, DevOps and MLOps have become part of the "secret sauce" for success... Take me there Components of your MLOps stack. The MLOps stack optimises the machine learning life-cycle by fostering collaboration across teams, delivering continuous integration and depl...
Read more

Digital Sovereignty in a Polarised World - Data, Cloud Power, and the Search for Trusted Alternatives

 Relationships have deteriorated, with trust diminished to an extent that may preclude restoration. The world, once structured to favour certain regions, has undergone significant shifts; for numerous countries, such advantages never existed. In this polarised reality, stakeholders are re-evaluating alliances, as former partners now often embody the role of "frenemy," thereby threatening freedom. This phenomenon is longstanding, rooted in historical power dynamics. When politics and influence supersede principles of fairness, respect, and integrity, ethical boundaries become blurred. Previously, issues that did not directly affect you would get overlooked out of principle, but current risks necessitate action to safeguard sovereignty. Information has consistently served as a key strategic asset, a trend only intensified by technological advancements that have elevated data as the principal factor. In other words, technology has amplified that, and data is the name of the game...
Read more

Assembling MLOps practice - part 1

In one of our previous articles it was highlighted how DevOps manages the End-to-End application cycle, leveraging agility and automation. CI/CD pipelines, collaboration and transparency, monitoring and automation are part of the list on how DevOps leverages and facilitates agility. What if then we bring those to support ML? That is how MLOps comes to the table and starts making sense! Lego Alike data assembly - Generated with Gemini A big tech corporation, or a startup, nowadays will see how it is becoming a requirement to incorporate AI and Machine learning (ML) in their operations. ML components are key parts of the ecosystem, supporting the solutions provided to clients. As a result, DevOps and MLOps have become part of the "secret sauce" for success.  What is MLOps Just to bring the definition of what you probably know (or put together based on the above) MLOps focuses on the life-cycle management of machine learning models. It combines machine learning with traditional ...
Read more

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.

Agreed