Gtmhub - The Ultimate OKRs Playbook - 052020
Gtmhub - The Ultimate OKRs Playbook - 052020
Gtmhub - The Ultimate OKRs Playbook - 052020
OKRs playbook
The Road to Agile Business
Best Practices For Adopting Objectives and Key Results (OKRs)
Table of Contents
Step 1: Appendix 1:
Understand why you want to adopt OKRs 3 Adopting OKRs checklist 13
Step 2: Appendix 2:
Understanding the basics of OKRs 4 OKRs examples 13
Who should own OKRs? Company OKRs
How many objectives? CEO OKRs
How many key results? Sales OKRs
Marketing OKRs
Step 3:
Select a pilot group 5 Product OKRs
Finance OKRs
Step 4:
Operations OKRs
Get buy-in from your teammates 6
HR OKRs
Step 5:
Set the basic rules 6 Appendix 3:
Common mistakes 15
Cadence
Too many objectives
Check-ins
Quantitative objectives
Maximum number of objectives
Qualitative Key Results
Maximum number of Key Results
Everyday work as OKRs
Retrospecive meeting cadence
OKRs as a TO-DO list
How will OKRs be set?
Step 6:
Appoint OKRs master 8
Step 7:
Set the OKRs cadence 9
Step 8:
Define Mission & Vision 9
Mission
Vision
Step 9:
Define Company OKRs 10
Annual objectives
Quarterly objectives
Step 10:
Derive Team & People OKRs 11
Step 11:
Set up regular OKRs review meetings 12
Step 12:
Review your first OKRs session 12
Step 1:
Understand why you want to adopt OKRs
OKRs bring many benefits to a business.
Some of the more common ones are:
— Focus
— Alignment
— Engagement
— Transparency
— Accountability
We have helped dozens of high-growth companies successfully implement
OKRs and we have learned that organizational focus is by far the
most important benefit, followed by accountability. Other benefits are
engagement, alignment and transparency.
Busy, productive, and innovative teams often lack focus due to what is known
as “shiny object syndrome”. There is always something new to be done and
lack of motivation is rarely a problem. OKRs provide a framework that does
not inhibit that motivation, but rather channels it towards accomplishing
prioritized goals.
An example…
Objective: I want to get fit.
The interplay between objective and key result is very clear. After all, what it
means to get fit will be different for every person. A skinny person may want to
put on 10 lbs. of muscle, while an overweight person may want to drop 5 lbs.
of fat.
Objectives are… always qualitative and aspirational. They are something that
you, your team, or your organization aim to achieve (and should not contain
numbers!)
Key Results are… always quantitative. They will tell you if you have achieved
your objective, so they should be measurable to avoid any doubt. Even a Yes
/ No key result is (really) numeric since the outcome is binary. For example,
“Pass an exam” is a valid numeric key result which can have for values either
Yes (1) or No (0).
Step 3:
Select a pilot group
Unless your team is comprised of five or less people, it is always a good idea
to select a few people to be your pilot group.
There are two basic approaches that companies employ when choosing
a pilot group: management or one function (e.g. engineering). Both
approaches have benefits and you should decide for yourself what makes
more sense.
Selecting the management team as your pilot group usually works very well,
because management is used to working against objectives. The objectives
will be more strategic and the alignment benefit of OKRs will shine. The
downside of this approach are that convincing entire management team to
participate in a pilot may not always be an option.
Going with one function as a pilot group has the benefit of seeing how the
process will work vertically, from the most junior to the most senior person in
that function. Additionally, other functions will be more eager to adopt OKRs if
they see it working in a peer team, than if it comes “down” from management.
It goes without saying that securing buy-in from teammates is critical for
adoption of any new process or practice, and OKRs are no different.
We have found that including your teammates early in the process and
shaping of the OKRs implementation is most successful.
Step 5:
Set the basic rules
You will find many “rules” when it comes to OKRs, but in practice – everyone
will tweak things at least a bit. In our experience, tweaking is great as long as
everyone is aware of it. Here we list some of the most important aspects that
will define your OKRs process.
Cadence
For what time period will the OKRs be set? Typically, companies use quarters,
but for organizations where things move and change rapidly, we recommend
opting for 4, 6, or 8 weeks instead.
Check-ins
How often should OKR owners update their key results? Generally acceptable
practice is once a week and, for whatever reason, most companies choose
Friday.
Bottom-up: Employees set their own OKRs based on what they think should
get accomplished. To make this work, company OKRs, mission and vision
should be clearly defined.
So, who would fit the role? In searching for an OKR Master of your very own,
keep in mind that the characteristics of a great OKRs Master are…
Process analogy…
OKRs master is a very similar role to Scrum master. It is a very much role that
supports the process, as opposed to a decision-making role. Just as a great
Scrum master helps team / scrum to excel at agile software development,
great OKRs master helps teams get most out of OKRs.
That being said, high-growth and smaller companies tend to move with a
higher velocity and things tend to change fast. To reflect this, many will go
with a shorter cadence. We have found that a six or eight week cadence
works best in a fast-moving environment.
Step 8:
Define Mission & Vision
While every company should have a mission and vision, it is absolutely
necessary to have those defined and well-known to everyone in companies
that adopt OKRs. Without mission and vision, your team will have a hard time
coming up with meaningful objectives.
Mission
Mission is the reason your company exists.
You can think of mission as the lasting overarching objective of your company.
All goals and objectives need to derive from it.
“To bring consumers foods that are safe, of high quality and
provide optimal nutrition to meet physiological needs. In addition to
Nutrition, Health and Wellness, Nestlé products bring consumers the
vital ingredients of taste and pleasure.”
Nestlé
Step 9:
Define Company OKRs
Before you and your team can start setting individual and team objectives,
company objectives need to be set. Employees and teams are there to help
company achieve its objectives.
A fairly common approach is for company to set both annual and quarterly
objectives and we advise high-growth and early stage companies to do the
same.
Annual objectives
The annual company objectives should be the most important and ambitious
objectives that will help company achieve its mission and execute against
its vision.
Examples:
— Drive more upsell and cross-sell
— Become a thought leader in our industry
— Grow faster than market
Note, that depending on the size of your company you may very well have
more than 3 annual objectives – however, keep in mind that OKRs are all
about focus. We highly advise having anywhere between 3 and 5 annual
objectives.
Quarterly objectives
Once you have your mission, vision and annual objectives in place – defining
the objectives for your first quarter should be pretty straightforward.
For example:
— Improve upsell of our entry level customers
— Get media coverage
— Deliver a new vertical solution
Step 10:
Derive Team & People OKRs
At this point, you have done the lion share of work. You have set the mission
and vision of the company. You have also defined the annual and quarterly
objectives for your company.
What is now left is to see how your team will help your company achieve its
objectives.
Step 12:
Review your first OKRs session
Once the planning period finishes, you should organize an all-hands meeting
to discuss the results. This is often overlooked in companies which tend to
move quickly and always look forward. The all-hands review of the past OKRs
session is tremendously important for several reasons:
— It demonstrates how serious a company is about OKRs. If things get done
and no one notices, it doesn’t really matter.
— It is a chance to give credit to people that excelled at their OKRs
— It is a learning opportunity for people and company as a whole, to see
where things didn’t go well and how they could be improved
Appendix 2:
OKRs examples
Company OKRs
Objective: Make company profitable
CEO OKRs
Objective: Build a world class team
Sales OKRs
Objective: Reduce sales lifecycle
Key result 1: Sales lifecycle for entry level edition below 5 days
Marketing OKRs
Objective: Nail the value proposition on the homepage
Finance OKRs
Objective: Improve annual budgeting process
Key result 2: Get budget proposals 30 days earlier than last year
Key result 3: Close the final budget 15 days earlier than last year
Operations OKRs
Objective: Become a data-driven company
HR OKRs
Objective: Make the life of employees more pleasurable
Why is it a mistake?
Companies that embrace OKRs are looking to improve their focus and
accountability. By setting too many objectives, both of these benefits will be
hindered. In our experience, when there are too many objectives none tend to
be accomplished and people get demotivated, while the company as a whole
concludes that OKRs are not the right approach.
The obvious answer is not to have too many objectives, keep them to 3 or
less. In practice, however, you may encounter pushback from your peers and
employees. What we have found is a good approach to dealing with this is
following: tell everyone that, of course, they may do as many things as they
want – but that you want only the most important 2-3 objectives defined as
OKRs. This is a good compromise to get the ball rolling and reality will kick-in
soon enough and take care of the rest.
Quantitative objectives
Objectives should be inspirational; they should motivate your team.
Why is it a mistake?
There are several reasons why this is a problem.
The purely technical reason is that you will have trouble defining key results for
an objective that is already quantitative and you may end up running in circles.
Third problem is that you are setting only one number. Here is an example of
how this is problematic:
Why is it a mistake?
It is a mistake because you will not have unbiased way of measuring whether
you are achieving your objective or not.
Why is it a mistake?
A typical example here is an accountant in the company. Every month
accountant needs to do the payroll. That, however, is not an objective – that is
just simply something that needs to happen.
Why is it a mistake?
Unfortunately, effort is not always rewarded with results. Sometimes, we may
work very hard only to see in the end that our effort was misguided and we
have not achieved whatever it is that we’ve hoped to do.
Key results: How are we going to know that we have achieved it;
definition of success
Now, armed with this definition we can see how OKRs should not be tasks.
Let us examine following examples:
Bad objective: Release new version of the software. The reason this is a
bad objective, because no one actually releases software for the sake of it.
Perhaps we are releasing it to make software more stable or more engaging.
Both “Make software more stable” and “Make software more engaging” are
good objectives, because they are qualitative and communicate well our
intention.
Bad key result: Release new version of the software. This is a bad key result,
because the fact that we have released a new version of the software in no
way measures that our software has become more engaging or more stable.
A better key result would be “Decrease the bug reports by 20%” or “Increase
average logins by 10%” – as those would be good measures of our progress
towards the objective
Now, releasing a new version of the software is a good task that supports our
objective and will hopefully have an effect on our key results.
17