
OKR’s may seem like ordinary office jargon (OKR is literally an acronym), but actually, OKR or “Objectives and Key Results” is a goal-setting technique that sets challenging goals-against measurable actions. It is used by companies- operations, software, product, marketing, etc. to implement strategy and execute it. OKR allows setting goals, track their progress, and alignment against to achieve measurable results.
Before I go on and on about OKR’s, a background would be essential to understand OKR’s better. This story involves 3 people- 1. Peter Drucker founded MBO’s, 2. Andy Groove, who gave OKR’s (at Intel) and taught them to John Doerr. 3. Jon Doerr- who gave the acronym ‘OKR’ and introduced it to Google’s founders.
Now, the plot: The framework of what would eventually become Objectives and Key Results came from Intel, where Andy Grove implemented Peter Drucker’s Management by Objective system (MBO’s). OKR’s foundation is based on MBO’s. A critical difference between OKR’s and MBO’s is that OKR’s are quarterly, and OKR’s are not tied to compensation.
John Doerr, who learned this from Andy Grove, named this entire concept ‘OKR’ and introduced this philosophy to Google’s founding team in 1999. Google adopted this to set their company’s strategy, and if you’ve googled this, you know the rest is history!
Additionally, many big names have adopted OKR’s- LinkedIn, Netflix, Amazon, Spotify, etc. They have used OKRs to manage their company’s goals, and the alignment has allowed them not merely to survive but thrive at their goals.
Let’s go back to the basics.
OKR’s are a goal-setting methodology that helps employees prioritize, align, and measure the outcome of their efforts. OKR helps companies bridge the gap between strategy and execution and move from an output (short term, direct result) – to an outcome-based approach to work (effectiveness).
OKR INVOLVES- OBJECTIVES, KEY RESULTS, AND INITIATIVES.
In this, we will discuss the 3 main aspects of OKR’s and how to write effective objectives, key results, and initiatives.
1. Objectives: An Objective is a description of something that you’d/ the company would like to achieve in the future. An Objective sets the direction. Objectives shouldn’t be technical and shouldn’t contain a metric so that everyone understands where to go- thus, qualitative. The best-written objectives are ones that the team understands. The objective is the goal set which is usually time-bound (quarterly)
a. Speak the Team– CEOs and Managers may get ticked with words like 5% traction or conversion, but we mere mortals speak in terms of progress and growth. Thus, objectives should be set in the ‘team’s language’- everyone should be on the same page, to begin with. If the team believes in ‘kill it,’ ‘awesome,’ then use it. If they want ‘transform’ or ‘growth- do that. The objective should speak for the team.
b. Time– Objectives should be team bound- mostly quarterly. The objective should have a precise time and should be set to be doable in that time frame.
c. It should be for YOUR team– Objectives should be set such that it doesn’t find its way to blame other teams/departments in case of failure. It shouldn’t read as ‘Marketing team failed to capture market’ or Sales failed to sell. The objective should be doable- in a time frame by the team who have set it.
Examples of a good objective:
Examples of Bad Objectives:
Why are they wrong? Mainly because they look like Key results rather than Objectives.
Objectives are NOT a commitment- they are just giving a direction, so everyone is on the same page
2. Key Results– Key results are measurable outcome which is required to measure the objective. It usually contains a target value, and it is quantitative. It is a way to measure progress towards the objective. The critical results show much close you are towards achieving your objective.
Key results can measure growth, performance, revenue, performance, quality, or employee NPS.
Eg1: ->Objective– Make the customer support team more self-sufficient.
->Key Result– Reduce tickets by 10%
->Initiatives– Create a guide on the 20 most frequently asked questions.
Eg2: ->Objective- Be a top place to work in India
->Key result– Reach top 10 in ABC magazine’s Best startup to Work at in India.
->Initiative– Hire a People & Culture Manager.
OKR’s are not for everything. They are not for people management or control. Nobody likes micromanagement. OKR’s exist to make sure the team is on the same pa
They are just for making sure that critical strategic work is done. (software management). OKR’s work best when COMMUNICATING strategic questions or measuring hypotheses which you’ve derived (read: In the Eisenhower’s matrix on Important- Not Urgent) part and set an OKR around it. Do OKR’s around things you want to do but often don’t, or they seem non-urgent. An OKR around something you’d manage anyway is pointless.
For example: why build an OKR around electricity bills? You’d pay that anyway. Instead, creating an OKR around writing a draft would be more actionable, which you tend to procrastinate. And there are plenty of examples across many industries.
Additionally, In a team, Everybody decides the OKR’s. You should learn to trust people with OKR’s. Empowering people is how you keep your A players. If (incase) things go sideways -> you coach, OKR’s cannot be the metric to judge the entire team. Hire good people, and trusting them is the key. OKRs just exist to make sure things are aligned.
Further, OKR is not a ‘commitment.’ If you’re committed to a project, you’re stuck with a project. But if you commit to a result, you have the flexibility to adjust as you get new information. OKR’s allow that flexibility, and that is one of its key advantages.
If you cannot choose between what is critical strategic efforts, try sequencing. Are there things you could do first that would make another effort more effective? Should you improve the customer experience before spending a bundle on advertising? And if that doesn’t work, try to narrow them down to as few as possible and rank them by importance.
EngageWith is a reward and recognition tool that allows:
Making your team feel a-OK with OKRs can be game-changing. As managers, we must make sure the team is aligned but not micromanaged. OKR’s help you achieve just that. Trust your team and trust their OKR’s.
