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

Apple's App Tracking Transparency sealing Meta's fate

Anonymous
If you have been following the recent news on Meta (formerly Facebook) you may have read that Meta recently projected their ad revenue will be cut by a staggering $10 billion in 2022 due to Apple’s new App Tracking Transparency feature (also known as ATT). This has resulted in Meta’s stock to plummet by over 20%. Photo by julien Tromeur on Unsplash - modified by Beolle So what is Apple’s ATT and how does it impact ad revenue? Apple has been releasing multiple privacy features for the last few years. This included Apple’s Mail Privacy Protection and Apple’s App Tracking Transparency feature. You can learn more about Apple’s Mail Privacy Protection in our earlier post by clicking here .  Apple’s App Tracking Transparency (ATT) was launched in iOS 14.5 and iPadOS 14.5 where it prompted users to select if they wanted the app to track their activities across other apps on the device. The prompt is displayed when the user opens an app like Facebook or Instagram for the first time o...
Read more

Building MCP with TypeScript

MCP servers are popular these days. We’ve been researching and exploring a few code repos, some where missing modularity, others just not having pieces that we were looking for… therefore we decided to build our own, simple and foundational that could be a starting point for those trying to solve for the similar things we were… and we decided to share it with the community, via our public github. MCP host, server,data sources     Before we start.  Using Typescript and NodeJS was one of our requirements. This proved somewhat challenging because I don't code as frequently these days due to my leadership responsibilities, and I typically prefer working with C# or Python. Colleagues in my tech community have been working with their teams on some of their MCPs going the Python route. Therefore, I said, “I guess we are trying the other route” 😊. One of our reasons to go with TypeScript was due to the need of the integration with APIs, and based on the research, it seems t...
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

SLA-SLO-SLI and DevOps metrics

Companies are in need of the metrics that will allow them to stay in business by making sure they meet the expectations of their customers. The name of the game is higher customer satisfaction by winning their trust and loyalty. To do so, you want to provide good products and services. Therefore you need to find ways to monitor performance, drive continuous improvements and deliver the quality expected by the consumer in this highly competitive market. Photos from AlphaTradeZone via Pexel and Spacejoy via Unsplash SLAs, SLOs and SLIs are a good way to achieve the above. They allow clients and vendors to be on the same page when it comes to expected system performance. If we go one level deeper, vendors/providers work on NFRs (Non-Functional Requirements) when working on their solutions. NFRs define the quality attributes of a system. I bring them up because the relationship between them and the SLAs is that they provide, in a way, foundational aspects for the SLA-SLO-SL...
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