The biggest OKR mistake is turning objectives into a to-do list
Leaders finish an inspiring town hall on vision and strategy, and employees walk back to their desks with no idea how it changes their daily work. Rutuja Joshi, an Agile and OKR coach at LogMeIn who has coached teams across continents, has sat in those meetings herself. So what does an objective need to look like to drive real change instead of becoming one more task list?
Learn to write two or three audacious objectives backed by key results you can actually measure
Agile and OKR coach Rutuja Joshi explains how teams can design effective Objectives and Key Results, starting from purpose, vision and mission rather than a task list. She shows how to write two or three audacious objectives backed by measurable key results, and argues that OKRs work only when they are collaborative, transparent and kept separate from performance appraisal and pay.
“It has to have this outcome driven value driven intent in there, and it should make you positively uncomfortable.”
“She always says that, hey, it's not a key result unless you have a number in it.”
What you will learn
Distinguish an objective (what you want to achieve) from a key result (the measurable benchmark of how you get there).
Ground every OKR set in a clear purpose, vision and mission before writing any goals.
Limit a quarter to two or three objectives with three or four SMART key results each, keeping tasks beneath the key results.
Avoid linking OKRs to appraisal, compensation or hiring and firing so teams feel safe setting audacious goals.
Run the OKR cycle of definition, weekly check-ins and blame-free reflection to keep teams aligned and autonomous.
Key takeaways from the speaker
An Introduction to Objectives & Key Results as a Goal setting framework.
Stories from Google, Intel, Gates foundation on their success with OKRs.
Why do OKRs work? Why does your company need them? What does an effective objective look like?
How to put good ideas to great execution?
Details
Level
Beginner
Format
Talk
Technical depth
Non-technical
For
People manager, Mid-career
Length
19:29
Published
July 2021
Questions this talk answers
What is the difference between an objective and a key result?
An objective is the simple what statement of the goal a team wants to achieve. A key result is a SMART benchmark, ideally with a number, that tracks progress towards that objective.
What should a team do before writing OKRs?
Leaders should first communicate purpose (why we exist), vision (what impact we want to create) and mission (how we get there). OKRs then translate these into day-to-day work.
How many objectives and key results should a team set?
Joshi recommends no more than two or three objectives per quarter, each with three or four key results, because fewer goals mean more focus and less cognitive load.
Should OKRs be tied to performance reviews or pay?
No. She asks companies not to link OKRs to appraisal, compensation or hiring and firing, because OKRs are meant to be intrinsically motivating and to create psychological safety.
How are OKRs different from KPIs?
A KPI is a metric that gets tracked without explaining why. OKRs add intent and meaning, prompting conversations about why a goal matters and why it is measured a particular way.
About this talk
OKRs (Objectives and Key Results) is a goal management framework helping companies focus on the things that matter.
By aligning teams, departments and individuals, OKRs provide a framework for measurable strategic outcomes to stretch and motivate, improving performance and growth. Progress is tracked and realised in a regular, repeated cycle of target and achievement.
In this OKR Session, I will provide a comprehensive overview to the audience to the method that originated at Intel, were taken up by Google and are now the goal setting tool of choice at many well-known multinational enterprises.
From inspiring town hall to clueless at your desk (66 s)
Why OKRs must never be tied to pay (88 s)
Alignment versus autonomy: cross the river (69 s)
So, good morning, good afternoon, good evening. I can see people from different geographies and it's so exciting to be here. For the last two days, I have been listening to a lot of awesome speakers and it's a great honor to share the stage with such amazing people out here. So, once again, welcome to this session. For next 20 minutes, we are going to deep dive. I mean, at least we'll try in this topic of OKRs. A little about myself. I'm Rutuja. I work as an Agile and OKR coach with LogMeIn and I'm based out in Germany.
So, for my last more than a decade, I have tried different frameworks with Agile, Lean and OKRs and I think it's a continuous journey of learning. And today, I'm going to just share a couple of things which I learned from my OKR journey in the last couple of years. Speaker 1: Okay, so I hope you all can see my screen. We're going to talk about objectives and key results, OKRs. And the session is about how do we design effective OKRs for our team? How can you design your effective OKRs for your team?
Starting with OKRs. Now, OKRs is a acronym for objectives and key results. So let's look into what does it mean? What are OKRs? Objective is simply what is to be achieved. So what is an objective? It is nothing more, nothing less. It is that simple what statement. What is that statement? What is that thing? What is that goal which you as a team or individual or as an organization you want to achieve?
This is nothing but your objective. A key result is a benchmark which will help us to understand that how do we get to that objective? So the key results are nothing but how. So OKR is a goal setting framework. Speaker 1: There are many, many goal setting framework out there. Some organizations use KPIs, key performance indicators. Some use smart goals and OKR is one of them. Usually in OKR philosophy, they say KPIs with souls and intent is nothing but OKRs. So what are objectives and key results?
The goal setting framework. The objective is simply what is to be achieved and a key result is how do we get there? So this will benchmark. Speaker 1: We'll benchmark and monitor step by step progress towards this objective. Speaker 1: Now, a lot of times when I'm working with teams and organization, I have realized that the leaders just come with their team and they start talking about, OK, team, we as a team, what should be our goal?
Speaker 1: What should we achieve? What should we be working on in next couple of months? I mean, that's OK. That's a good approach. That's all OKR is about. But the most important layer or a step, Speaker 1: Before defining OKR is you start with a why. Now, what does this mean? Speaker 1: As an organization, it is the leader's responsibility to talk about purpose.
Speaker 1: Purpose is nothing but why do we exist? So as leaders, as managers to your team, it is important that you communicate the purpose of your existence. Speaker 1: Why do we exist as an organization? Why do we exist as a team? Why do we exist as a product? So it is very, very important that we start having conversations around the purpose.
Speaker 1: After purpose, it is important to talk about vision. Now, what is vision? What impact do we want to create in the world for what we exist? So purpose? OK. This is why we exist. And vision is what impact do we want to create? What value do we want to build? Speaker 1: What value do we want to bring in the world for what we exist? Following the vision? It's mission. Now, mission is this. How do we achieve this? How do we get to this vision and purpose?
Speaker 1: So it's very, very important that before you start setting OKRs or bringing goals to your team, to your department, to your organization, you start with purpose, vision and mission discussion and conversation and communication. Speaker 1: So I think this is the starting point which we have to handle before we jump into defining OKRs. Speaker 1: So how is the flow? You first start with purpose, vision, mission.
Speaker 1: Now this purpose, mission, mission could also be around, hey, we are launching a new product. Speaker 1: We had this problem or a lot of users had this problem and we are thinking about launching a solution for this. Speaker 1: So this is our new idea and we want to translate it to a product. We want to build a product around this.
So this could also be a purpose, vision, mission around the product or around the department or around a particular initiative. Speaker 1: Or on a very, very meta level, like on the org level. So it's totally fine that you can define purpose, vision, mission on different initiatives or different teams or products or as a whole organization. Speaker 1: When you define purpose, vision, mission strategy, OKR is that vehicle which will translate this into your day to day work, into your executionable work.
Speaker 1: Now, I remember working in the industry and many times I attended all hands meeting and town hall meetings where all the leadership came and they spoke about different strategies and our vision and what we want to achieve in next 10 years and five years. Speaker 1: And, you know, sitting in those meeting, it felt like, wow, I'm in such a great company.
Speaker 1: It's so inspiring and motivating. But then after those two hours of meeting, when I came back to my workplace on my table on my desk. Speaker 1: I started thinking, OK, now I have no clue that how do I translate this to my everyday world? Speaker 1: What should I do in my role in order to add value to this purpose, vision, mission?
Speaker 1: And this is exactly where OKRs come in place that OKR will help you and your team to formalize this goal, which will be aligned to your higher purpose, vision and mission. Speaker 1: OK, now look, let's look at some of the characteristics of objectives and key results. Speaker 1: So if you look at objective and objective has to be audacious, inspirational, meaningful, it should express goals and intent.
Speaker 1: Now, a lot of times I have seen teams, they they come together, they sit with pen and a paper or maybe they open a conference page and they start writing their objectives. Speaker 1: And one of the biggest mistake which people do is they confuse objective to a to do list. Speaker 1: So an objective is not a to do list.
Speaker 1: It is not a task manager framework or it is not a task list. Speaker 1: It's it's something which is quite audacious. Speaker 1: It's something which you want to do in order to bring change. Speaker 1: So objective is something it has to be meaningful. Speaker 1: It has to have this outcome driven value driven intent in there, and it should make you positively uncomfortable.
Speaker 1: So please make sure that you as a team or individual should not convert your to do list as your objective. Speaker 1: It is not objective is purely a statement set of goals which will help you to drive some meaningful changes in your organization. Speaker 1: And this is what objective is all about. Speaker 1: On the other hand, key result, key result has to be smart.
Speaker 1: We mean by smart, it has to be specific, measurable, time bound, aggressive, realistic. Speaker 1: Marisa Meyer from Google, because Google is quite experienced practitioner of OKR. Speaker 1: She always says that, hey, it's not a key result unless you have a number in it. Speaker 1: So it's very important that you set a very, very audacious, meaningful value driven objective supported by three to four key result, which you can actually track within that timeframe.
Speaker 1: You can measure them and you can actually be very, very specific in terms of achieving those actions or those key results which are connected to your objectives. Speaker 1: Now, how do the OKR overall flow look like? Speaker 1: So I already told you, you will start at the mission statement. Speaker 1: Following the mission, you will have different objectives.
Speaker 1: So it could be two objective, three objective, four objective. Speaker 1: I usually tell teams to avoid more than three objective. Speaker 1: The reason is less is more. Speaker 1: So, and again, OKR philosophy, they say lesser the goals, the more focus you have. Speaker 1: And it's important to have control on your work in progress.
Speaker 1: So having 10 goals, 10 objectives for a quarter. Speaker 1: I'm not sure if it's pragmatic or realistic to be, you know, to be working on 10 goals at the same time. Speaker 1: Apart from that, it also adds a lot of cognitive load to your team, to individuals. Speaker 1: So it's very, very important that you tackle two to three objective in a quarter.
Speaker 1: Below these objective, you will start writing three to four key results for each objective. Speaker 1: And inside that, you may have your to-do list. Speaker 1: So I was talking about, hey, you may have list of activities, list of tasks, which you need to do. Speaker 1: Let's say every day in order to fulfill this key result, which will effectively add value to the objective.
Speaker 1: So definitely you may have task lists, but that needs to be jotted down under the key result. Speaker 1: So it has to start with mission, objective, key result, and following it, it has to be your tasks, activities, etc. Speaker 1: Now let's look at one of the OKR. Speaker 1: So I will show you the first OKR here.
Speaker 1: It's a diversity OKR, a diversity goal, increasing the diversity in the workforce of the organization. Speaker 1: Now, if you look at this objective, you know, it is talking about driving change. Speaker 1: So it is not like a very, very simple to-do list. Speaker 1: It is talking about changing the culture, driving some important change in the structure of the organization.
Speaker 1: Now, if you look at the key result, the key result could be women make up at least 40% of all the team members. Speaker 1: Next key result is women make up at least 35% of all the managers. Speaker 1: And the last one is increase the proportion of team members who belong to ethnic minority to 35%.
Speaker 1: Now, if you look at this, you can already get the idea that how the OKR model will work like. Speaker 1: Objective is really, really meaningful, something which will drive a lot positive culture or change in the organization. Speaker 1: And then you're talking about very, very specific, measurable, verifiable key result, which you will track on a very weekly basis and see, hey, my activity today.
Speaker 1: Is it contributing in this key result? Speaker 1: Oh yeah, this will move my key results. Speaker 1: Let's say from 10% to 20% or let's say from 20% to 22% and effectively this will add to my objective. Speaker 1: So this is how this whole OKR work like you start with a very, very meaningful intent goal followed following the key results.
Speaker 1: Okay, now a quick history. Speaker 1: How did it start? Speaker 1: So OKR started in a company called Intel. Speaker 1: And the grub, who was a then CEO of the company invented OKR framework there. Speaker 1: The beauty of OKR is it is not only top top down a character in a stick driven performance management kind of a system.
Speaker 1: It is not. Speaker 1: OKR is very much intrinsic, motivationally driven, engaging, collaborative framework. Speaker 1: So any company who is thinking to implement OKR, please do not link it to the performance appraisal of the people. Speaker 1: Please do not link it to the compensation part. Speaker 1: Please do not link it to the firing, hiring, because that's not the intent here.
Speaker 1: The intent of OKR is purely, hey, am I motivating my team to help them to break their own best record? Speaker 1: So it's all about how can we continuously improve and, you know, beat your own best record in the next iteration. Speaker 1: So it's a tool which was defined by Andy Grubb later on.
Speaker 1: John Deore learned it and then John Deore got it to other companies like Google and LinkedIn and Walmart. Speaker 1: And the beauty is it's very collaborative. Speaker 1: No one get fired if you feel on your OKR because it's all about, hey, how can we improve? Speaker 1: How can we improve these? Speaker 1: How can we remove these impediments?
Speaker 1: What is stopping our journey towards our goal? Speaker 1: So it's a it's a very motivating and engaging tool which help employees to come forward, create a lot of psychological safety, because come on, it's my goal. Speaker 1: I can go audacious. Speaker 1: No one is going to fire me here. Speaker 1: So OKR give this kind of mindset and culture to the to the organization.
Speaker 1: And I think this is how it is different from other goal setting frameworks there where Speaker 1: Even a little bit of failure may cause me, you know, some some after effects. Speaker 1: OK, so now another important thing why companies work with OKRs. Speaker 1: So it gives a lot of alignment. Speaker 1: I told you, OKRs are like top down and bottom up.
Speaker 1: So the manager comes with a list of OKRs to the team and the manager tell the team Speaker 1: that, hey, I think we should be working on these objectives based on what the leadership Speaker 1: have defined. Speaker 1: So the manager of the team comes with the OKR proposal and the team, on the other hand, also comes with the proposal that you're right, but we think that, hey, this is also Speaker 1: something we need to work on in this quarter or in this year.
Speaker 1: So in this way, you are collaborating top down and bottom up and that's a very aligned Speaker 1: way of defining your OKRs. Speaker 1: Engaging. I mean, imagine my manager asking me, what do you think about this goal for our team? Speaker 1: Do you think this makes sense? Speaker 1: It gives me a different level of motivation when I'm heard or when I'm participating Speaker 1: in defining the OKRs of my team.
So I think instead of top down, having collaboration and partnering is quite motivating. Speaker 1: Another thing, it gives focus and clarity. Speaker 1: I told you having two to three OKRs is the best way to do. Speaker 1: So handling 10 things at the same time, I wouldn't recommend. Speaker 1: Go for two to three simple, focused, defined OKRs.
Speaker 1: Then it is data-driven. Speaker 1: You are tracking your OKRs every quarter, every week, and it is transparent. Speaker 1: It is transparent to the manager, to the team, to the whole organization. Speaker 1: And it gives a lot of autonomy. Speaker 1: Autonomy to the manager, autonomy to the people. Speaker 1: So I think this is the whole beauty of OKR and that's why they say OKR is KPIs with soul and intent.
Speaker 1: Now this is a typical OKR setting guideline look like. Speaker 1: You start with all OKRs. Based on that, the department will define their OKRs. Speaker 1: Based on that, the teams will define their OKRs. Speaker 1: But you see, they are all interlinked. Speaker 1: They are all aligned horizontally, vertically, in diagonal way. Speaker 1: So they need to kind of make it transparent and align with each other.
Speaker 1: That how can we enable everyone to reach that objective? Speaker 1: Now this is one of my favorite picture from Spotify. Speaker 1: I'll just quickly tell you how OKR will take you to the most sweet spot in this matrix or in this picture. Speaker 1: Organizations who are always here in the low alignment, low autonomy, very, very bad state to be in.
Speaker 1: People are lost because they are not aligned. Speaker 1: The vision is not communicated to them. Speaker 1: And people are also not given autonomy to decide what should they work. Speaker 1: So we come for work. Speaker 1: I mean, we come from nine to six just to work and get our paycheck. Speaker 1: But there's no motivation.
Speaker 1: Talking about this section where the high alignment is there and low autonomy, the manager comes with the decision and tell the team what is to be done. Speaker 1: Again, not a sweet spot because we have hired smart people who can tell us how it is to be done rather than me telling them what to do and how to do.
Speaker 1: So again, not a very good spot to be in. Speaker 1: Another spot here where you have high autonomy and low alignment. If you see here, the leader is thinking that maybe the goal is clear to the team, and the team is, you know, there's a lot of autonomy. Speaker 1: The team is autonomous, but then they are not aligned.
They don't know the vision. Speaker 1: So they are just driving in different direction. Speaker 1: And ultimately, you know, no one is meeting that not star matrix or that ultimate success criteria, what matters the most for the organization. Speaker 1: The most sweetest spot here is this where you see the leader is saying, hey, we need to cross the river.
Speaker 1: And he's asking the team that, hey, figure out how. So this kind of sport is somewhere organizations should try to drive towards and OKR definitely helps organizations to bring, you know, teams and people to reach this level. Speaker 1: Now, this is the overall cycle of OKR. I already mentioned that we start with purpose, vision, mission.
Then you have OKR definition, OKR check-in. So you define OKR, you track your OKRs, and then you reflect on your OKR. Reflection is not blame game here. Reflection is all about why did we fail, what we could have done better. So it's kind of a retrospective. And this is how this whole cycle helps the team to be in time and, you know, focus on the most matter, mattering things, what they should be working on.
Speaker 1: All right. So with this, you can always reach out to me. That's my email ID and my LinkedIn. Please connect. And if you have any further questions, anything which I can help you with with regards to OKR, yeah, very happy to support. Any questions, you can share it in the chat because I think we still have three minutes to go.
We can take some questions. If it's here, any feedback, anything which you want to say, just feel free. Awesome. So, yeah, Ani, how OKRs are different from KPIs? Like I mentioned, KPIs are like you are just given this one key performance indicator, a metric that, hey, this is a metric. And now we track this. But we don't know why we don't know what is the intent behind tracking this matrix.
So OKR will make it more meaningful. So like I said, OKR is KPI with intent, meaning and soul. So OKR will guide the team to understand why we are doing this, why this is the most important goal. And you know why we have to track it in this way, why we are measuring this and not this. So there are a lot of these kind of conversation will happen within the teams and departments, which will make it more meaningful.
So this is how OKR is different from KPIs. Simone said, I find that OKR also works well with other goals. Like, yeah, absolutely. Absolutely. Totally. So OKR can combine with different different frameworks. So recently I'm also writing a blog around how do we combine OKR with Scrum, which is another powerful framework. So definitely this is this is totally doable.
And yeah, you can use it, implement it in any kind of ecosystem, any kind of team structure. So there's no, yeah, there's no kind of border defined here. Thank you, Ani. Thank you, Simone, for your questions. Thanks for joining in. And like I said, if you have any more questions, feel free to approach and keep OKRing. Thank you very much.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
How to write OKRs that turn vision into daily work
Agile and OKR coach Rutuja Joshi explains why objectives must start from purpose, stay few and audacious, and never become a performance stick.
In short
Effective OKRs begin with a team's purpose, vision and mission, not with a list of tasks. Rutuja Joshi, an Agile and OKR coach at LogMeIn, argues that a team should set only two or three audacious objectives per quarter, each backed by three or four measurable key results. She also argues that OKRs only work when they are collaborative, transparent and kept well away from appraisal and pay.
Key takeaways
An introduction to Objectives and Key Results as a goal-setting framework.
Stories from Google, Intel and other organizations on their success with OKRs.
Why do OKRs work? Why does your company need them? What does an effective objective look like?
How to turn good ideas into great execution.
Start with why, before any goal
Joshi defines the framework simply: the objective is what a team wants to achieve, and the key result is the benchmark that shows how it gets there. Many leaders open goal setting by asking the team what it should achieve next quarter. She says that is fine, but it skips the most important step, which is a conversation about purpose.
After purpose comes vision, the impact the team or organization wants to create, and then mission, how it plans to get there. These can apply to a whole organization, a department, a product or a single new initiative. OKRs are the vehicle that turns them into daily, executable work. Joshi describes leaving inspiring all-hands meetings about five- and ten-year plans, then sitting back at her desk unsure what to do differently.
"I started thinking, OK, now I have no clue that how do I translate this to my everyday world?" (5:34)
What good objectives and key results look like
According to Joshi, an objective should be audacious, inspirational and meaningful, and it should express intent. The most common mistake she sees is teams opening a page and writing down their tasks.
"And one of the biggest mistake which people do is they confuse objective to a to do list." (6:20)
An objective should drive meaningful change, and "it should make you positively uncomfortable" (6:38). Key results, by contrast, must be SMART: specific, measurable, time-bound, aggressive and realistic. She cites Marissa Mayer of Google, a long-time OKR practitioner:
"She always says that, hey, it's not a key result unless you have a number in it." (7:23)
Fewer goals, clearer structure
The structure Joshi recommends runs from mission, to objectives, to key results, and only then to tasks and activities, which belong beneath the key results they move. She advises teams to avoid more than three objectives in a quarter, because fewer goals bring more focus and keep work in progress under control.
"Apart from that, it also adds a lot of cognitive load to your team, to individuals." (8:35)
Her worked example is a diversity objective about increasing diversity in the organization's workforce. Its key results are concrete: women make up at least 40% of team members, women make up at least 35% of managers, and the proportion of team members from ethnic minorities rises to 35%. Teams track these weekly and ask whether today's activity moves a key result, for example from 20% to 22%.
Keep OKRs away from appraisal and pay
Joshi traces OKRs to Intel, where then CEO Andy Grove created the framework, and to John Doerr, who later brought it to companies such as Google, LinkedIn and Walmart. She stresses that OKRs are not a top-down, carrot-and-stick performance system.
"So any company who is thinking to implement OKR, please do not link it to the performance appraisal of the people." (11:15)
The same applies to compensation and to hiring and firing. Instead, the intent is continuous improvement: "The intent of OKR is purely, hey, am I motivating my team to help them to break their own best record?" (11:39). Because nobody is fired for missing an OKR, people feel safe setting audacious goals, which builds psychological safety.
Why OKRs work: alignment with autonomy
Joshi lists the benefits: alignment, engagement, focus and clarity, data-driven tracking, transparency and autonomy. Alignment comes from combining top-down and bottom-up proposals. The manager brings objectives based on leadership's direction, and the team brings its own.
"I mean, imagine my manager asking me, what do you think about this goal for our team?" (13:28)
She uses a picture from Spotify that maps alignment against autonomy. With low alignment and low autonomy, people come to work just for a paycheck. With high autonomy and low alignment, teams drive in different directions. With high alignment and low autonomy, managers dictate both what and how. The sweet spot is high on both.
"The most sweetest spot here is this where you see the leader is saying, hey, we need to cross the river." (16:06)
The OKR cycle then runs from purpose, vision and mission to definition, weekly check-ins and reflection, which she frames as a retrospective rather than a blame game. In the Q&A, she describes OKRs as "KPI with intent, meaning and soul" and notes they combine well with other frameworks such as Scrum.
Watch the talk
Design effective OKRs for your team, Rutuja Joshi, about 19 minutes: https://www.womentech.net/video/design-effective-okrs-your-team
About the speaker
Rutuja Joshi is an Agile Coach at LogMeIn, based in Dresden, Germany, and an Agile and OKR coach with more than 10 years in the software industry, 8 of them in agile environments. She has coached agile teams internationally and works to bring clarity and focus to teams while promoting the right mindset and culture in organizations.
Questions this talk answers
What is the difference between an objective and a key result?
What should a team do before writing OKRs?
How many objectives and key results should a team set?
Should OKRs be tied to performance reviews or pay?
How are OKRs different from KPIs?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
OKRs
KPIs
SMART goals
Purpose, vision and mission
Spotify alignment and autonomy matrix
Scrum
Cite this talk
Rutuja Joshi. "Design effective OKRs for your team." WomenTech Network, 2021. https://www.womentech.net/video/design-effective-okrs-your-team