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 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.

Example of product worldview


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: 

Example of HOSKR framework

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


Trending posts

AWS Lambda and containers

Did you know that you can package and deploy containerized AWS Lambda functions? This capability was introduced in 2019. Amazon AWS also provides base images in Python, Nodes, Java, .Net, and other supported runtimes. Photo by Tom Fisk from Pexels There are prerequisites and limitations which you can take a deeper dive in this article from AWS documentation. In general, consider Lambda for event-driven applications, meaning for solutions that are not continuously running.The AWS Lambda container approach supports: Consistency in the set of tools used for the Lambda-based applications Your image can be up to 10 GB You get the same benefits as the function packages, such as familiar container tooling, automatic scaling, high availability, and others There are existing base images for Lambda, available on ECR public and Docker hub that you can leverage In addition, AWS has made available a set of packages  that implement the Lambda Runtime API, allowing developers to seamlessly extend th

Essence of email deliverability - SPF, DKIM, DMARC and segmentation

Recently I attended a lively discussion on email deliverability hosted by Litmus, one of the leading providers of email marketing tools. As email marketers one of the core metrics we often rely on is email deliverability and the discussion was around how to improve the email deliverability in today’s world where our audiences are ever inundated with emails. In addition we often find ourselves operating in a very competitive landscape vying for these audiences' precious attention. Photo by Ivan Samkov from Pexels   Hence it’s becoming increasingly important to ensure our emails are reaching our audiences’ inbox and driving engagement. This is why email clicks and engagement are strong indicators of the performance of our email campaigns instead of just the delivery rate of our campaigns partly thanks to Apple’s Mail Privacy Protection . So let’s start with the distinction between email delivery and email deliverability . This is very well articulated by Dimiter Batmaziam in the Li

Adobe Summit 2022 - Email nurturing takeaways

I had the pleasure of attending a number of sessions at the 2022 Adobe Summit and one of those sessions was by Don Mayberry on the importance of email nurturing in driving business outcomes. Don shared many interesting perspectives on email nurturing and strategies that really resonated with me. Don described these concepts through the lens of Marketo Engage but they can be easily applied using other marketing automation tools in the market including Adobe Campaign Classic, Salesforce Marketing Cloud, HubSpot, etc.  Photo by Richard Horvath on Unsplash Here are the key three (3) takeaways: Don compared the importance of nurturing email campaigns in generating sales to the nurturing of a young plant until it bears fruit. He highlighted that nurturing email campaigns may not lead to sales conversion right away however if done correctly it will sow the seed for future conversions. Don shared six (6) nurture tracks for email marketing.  The Red Carpet Track - An example of this is

Adobe Summit 2022 - Experience Platform

 Our hero image features many air balloons flying, scattered in a blue sky. Each of them has characteristics in their designs that are “part of a whole”, which in this case is an exhibition that is part of a festival. Now, let us leverage this analogy, mapping it to the elements that are relevant for this post’s agenda. Think about the pieces of data scattered through different systems, which combined (behaviour and PII data) becomes part of a whole: an enriched consumer profile that can provide you a “360 view”. This allows corporations to find opportunities, and turn them into value: “enabling ways to engage with that customer(s) to meet a cluster of business goals.” Photo by Lad Fury from Pexels   The objectives for this article are: To provide our takeaways from two (2) Adobe summit 2022 sessions, related to the Adobe Experience Platform and Real-time CDP (Customer Data Platform). Those sessions being S401 (AEP a modern foundation - by Klaasjan Tukler) and  S408 (DMP vs CDP:

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