OKR vs. narrative — which one should come first?

Product Narrative
Product Narrative Publication
4 min readFeb 28, 2019
Photo by bruce mars from Pexels

Author’s note (2021.06.07): Hello, we’re moving most of our articles to our website. Our articles — including this one — and brand-new materials can be found there. Thus, you can read this article here or on our website. Thank you!

Welcome to Shared Narrative #16!

We’d like to share with you updates regarding our engagement with the company we’ve been working with for over a month now. Our engagement started with interviews with the leadership teams, in which we applied and practiced empathic listening and active listening (both of which are covered in the 14th and 15th newsletter). These interviews are meant to give information about the company’s current situation, challenges, purposes, value proposition, etc. We did 10+ interviews to cover the leadership rank.

Two values we extracted from these interviews. First, they made us understand the company one level deeper. We noted how the teams interact with each other, their day-to-day tasks, and how each leader leads. Second, the insights we constructed from those interviews helped us create more relevant narratives for the company.

When we shared these benefits with the leadership team, one of them asked: which should come first: the narrative or the OKR? Apparently, a one-day meeting to set the top-line OKR had been scheduled to happen in less than a week, whereas we didn’t yet have an agreed-upon narrative.

Our answer was either one could come first. The OKR may come first or the narrative. They are complementary to one another, but there is no causality between OKR and narrative.

In this particular engagement, we’re creating narratives based on the agreed-upon OKRs. The chronology was the teams came up with the OKRs, only then we built up the related narratives for them. The important note here is for each Objective, we discussed the rationales behind it. The rationale represents the reason as to why they decided to pick that Objective; what made that Objective more important than the others.

For example, one Objective (O) is related to becoming the leading payment solution in the e-commerce industry in Indonesia. (For confidentiality, we use the generic term “payment solution”). The heated discussions about why they decided to become the #1 player actually revealed an understanding that this particular sector of the e-commerce business tends to favor only one winner. It’s a winner-takes-all game. Thus, the team decided to own it as the top-line objective.

To come up with the rationale, we listed down the supporting data such as the total addressable market, current number of transactions, relevant competitors, etc. How would that compare to the competitors? How much increase in market share should we aim for in the first half of 2019? Everyone shared their opinion and discussed extensively until we were certain we arrived at the right Objectives. This was essentially a prioritization exercise: to decide which Objectives were more important and why.

Discussing the rationale behind each Objective has several benefits. First, it facilitates the discussion between participants to ensure the same understanding as to why they choose that Objective. Second, since the rationale is based on data, not mere opinion, it helps participants look at the current situation more objectively. How did they do in the last year? Which areas to be improved? Third, a clear rationale also helps us to come up with the right Key Results faster.

Having a well-defined rationale also helps us to create a narrative because we understand why they chose that Objective. We understand the importance and significance of the Objective. In other words, knowing the rationale makes it easier to create the content for the narrative. While it’s true we need more than just the rationale to create the whole content, but the rationale helps to set the tone and direction for the narrative. In our case, even though we had conducted interviews and got useful information, the rationale informed us which information was relevant to a narrative related to a specific OKR.

In conclusion, it is entirely possible to create a narrative even if the OKR comes first. The key is knowing the reason behind the OKR, or in other words, the rationale. The next article will discuss the opposite: what happens when the narrative comes first and how to create the OKR based on the narrative.

Sponsor

Inspiration on the go

PS: Click here if you are interested in being a sponsor for Shared Narrative.

Want to find out more . . .

Check out our website to find out why we set up Product Narrative.

Or you can read past editions of Shared Narrative here: #4, #5, #6, #7, #8, #9, #10, #11, #12, #13, #14, #15

Visit our blog to read more articles and writings like this.

Have a great weekend!

— The Product Narrative Team

PS: if you haven’t subscribed, click here to receive regular updates and insight about OKR, narrative communication, and people ops.

--

--

Product Narrative
Product Narrative Publication

We help company leaders add more hours to build their business — by coaching their teams to self-manage to support the shared company goals.