Skip to main content

Goal setting frameworks for Product Management - OKR and HOSKR

[PLACEHOLDER]


As a business analyst and product manager we often use various frameworks to synthesize and organize our product ideas and goals. I think of frameworks as tools in our product management tool kit which we use depending on the task at hand. 

And speaking of goals, OKR is a very popular framework that I often use to set the goals for the products I am managing. However recently I participated the #ProductCon conference hosted by Product School and I stumbled upon one of the talks in which Rapha Cohen, the CPO at Google Waze introduced a more effective framework for setting product goals. The framework is called HOSKR. 

In this post I'll describe both the OKR and HOSKR frameworks in more details using examples. I hope this will provide you, our readers, more practical insights on how to effectively use these frameworks to set your product goals. 


OKR

OKR stands for Objectives and Key Results. If you are reading this post then you are on our Beolle blog and I am going to use one of the OKRs of our Beolle blog to explain the framework. 

An example of an OKR for the Beolle blog is outlined below:


OKR with example


HOSKR

HOSKR stands for the following: 

Hypothesis

Objective 

Signal 

Key Results

According to Rapha before a product manager can apply HOSKR he/she must develop a qualitative worldview in which the product resides. For example, for the Beolle blog this worldview will look something like the following: 

In this example I chose to represent the worldview as a funnel however the worldview can be represented using any of the business analysis techniques including context diagrams as applicable. The worldview can also be represented using a combination of techniques if required.

HOSKR with example




Once the worldview is established then the hypothesis can be framed and the objective, signal and key results defined. 

An example of an HOSKR for Beolle blog is outlined below: 

HOSKR for Beolle blog



As you can see in the example HOSKR allows us, product managers to synthesize more details for our product goals. HOSKR also provides us a framework to find the link between the objective and the key results - the signal. One of the key guidelines for applying HOSKR is to continuously take the key findings post execution to better frame the worldview. This ensure that the worldview better reflects the reality in which the product resides at a given time.  

In conclusion I think both OKR and HOSKR are very useful frameworks for setting product goals and have an important place in a product manager's tool kit. While OKR allows us to quickly synthesize our product goals HOSKR allows us to define our product goals with more granularity. Hence I highly encourage my bellow product managers to use these frameworks to set more effective product goals. 


Credits, references and collaborations


Anonymous

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

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

SRE, DevOps and ITOps

 If you are wondering what the differences between the SRE and DevOps are, as well as how these roles work with ITOps within an organisation then you are not alone; and best of all you are on the right blog post. Often enough business units in a company get confused, assigning the ServiceNow or Jira tickets or any other ticketing system of your preference, to the wrong group, and even having the incorrect expectations when doing resourcing. Let us go through definitions, insights and scenarios that will help you understand the difference. DevOps software development operations - AI Generated When it comes to DevOps and SRE, then you might be wondering which practice came first. While SRE may have originated a bit earlier, internally at Google, DevOps came first publicly as a practice and started to be used by companies. A few years later was when Google decided to open SRE to the world after the publication of the "Site Reliability Engineering" book. Therefore, technically sp...
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

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