Objectives and key results

Last updated

Objectives and key results (OKR, alternatively OKRs) is a goal-setting framework used by individuals, teams, and organizations to define measurable goals and track their outcomes. The development of OKR is generally attributed to Andrew Grove who introduced the approach to Intel in the 1970s [1] and documented the framework in his 1983 book High Output Management .

Contents

Overview

OKRs comprise an objective (a significant, concrete, clearly defined goal) and 3–5 key results (measurable success criteria used to track the achievement of that goal). [2]

Not only should objectives be significant, concrete, and clearly defined, they should also be inspirational for the individual, team, or organization that is working towards them. [3] Objectives can also be supported by initiatives, which are the plans and activities that help to move forward the key results and achieve the objective. [4]

Key results should be measurable, either on a 0–100% scale or with any numerical value (e.g. count, dollar amount, or percentage) that can be used by planners and decision makers to determine whether those involved in working towards the key result have been successful. There should be no opportunity for "grey area" when defining a key result. [3]

History

Andrew Grove popularised the concept of OKR during his tenure at Intel in the 1970s. [5] He later documented OKR in his 1983 book High Output Management . [6]

In 1975, John Doerr, at the time a salesperson working for Intel, attended a course within Intel taught by Grove where he was introduced to the theory of OKRs, then called "iMBOs" ("Intel Management by Objectives"). [7]

Doerr, who by 1999 was working for venture capital firm Kleiner Perkins, introduced the idea of OKRs to Google. [8] The idea took hold and OKRs quickly became central to Google's culture as a "management methodology that helps to ensure that the company focuses efforts on the same important issues throughout the organization". [7]

Christina Wodtke's 2016 book Radical Focus popularised the concept of OKRs through a fable about a young startup.[ citation needed ]

Doerr published a book about the OKR framework titled Measure What Matters in 2018. Grove's simple but effective concept is explained by John Doerr in his book: [7]

The key result has to be measurable. But at the end you can look, and without any arguments: Did I do that or did I not do it? Yes? No? Simple. No judgments in it.

Larry Page, former CEO of Alphabet and co-founder of Google, credited OKRs within the foreword to Doerr's book: [7]

OKRs have helped lead us to 10× growth, many times over. They’ve helped make our crazily bold mission of 'organizing the world’s information' perhaps even achievable. They've kept me and the rest of the company on time and on track when it mattered the most.

Since becoming popular at Google, OKRs have found favor with several other similar large tech organizations [9] including LinkedIn, [10] Twitter, [11] Uber, [12] Microsoft [13] and GitLab. [14]

Best practices

Doerr recommends that an organization's target success rate for key results be 70%. A 70% success rate encourages competitive goal-making that is meant to stretch workers at low risk. If 100% of the key results are consistently being met, the key results should be reevaluated. [7]

Organizations should be careful in crafting their OKRs such that they don't represent business as usual since those objectives are, by definition, not action-oriented and inspirational. [15] Words like "help" and "consult" should also be avoided as they tend to be used to describe vague activities rather than concrete, measurable outcomes. [16]

When coming up with key results, it is also recommended to measure leading indicators instead of lagging indicators. Leading indicators are readily measurable and provide organizations with an early warning when something isn't going right so they can course-correct. Conversely, lagging indicators are those metrics which can't be attributed to particular changes and so prevent organizations from course-correcting in time. [17]

Ben Lamorte, author of The OKRs Field Book, suggests 5 best practices for OKRs coaches: [18]

  1. "Less is more" - define a small set of OKRs
  2. "Crawl-walk-run" - Deploy OKRs piecemeal. Begin with pilot teams rather than a full-scale deployment across an entire organization. In the first cycle, emphasize learning about OKRs. Reserve the second cycle to explore how best to scale the program,
  3. "Outcomes, not output" - Write key results that mostly reflect outcomes (results) rather than output (amount of work delivered)
  4. "OKRs are not everything" - Write OKRs that reflect the most important areas to make measurable progress rather than attempting to reflect everything you do. Distinguish OKRs from tasks and health metrics. Health metrics are monitored and important to track, but, unlike key results, they are not the focus for near-term improvement
  5. The only way to learn OKRs is to do OKRs


Once planning and crafting OKRs is done, teams have the crucial task of managing their work effectively throughout the OKR cycle. Businessperson and author Christina Wodtke recommends setting a weekly cadence to ensure progress toward the goals is achieved.

In her framework, [19] Wodtke suggests answering the following questions every Monday:

  1. What is the team's confidence in achieving the OKRs?
  2. Are the team's Health Metrics in a good place?
  3. What are the most important things to get done this week?
  4. What should the team prepare for in the coming four weeks?

Criticism

OKRs were once typically set at the individual, team, and organization levels; however, most organizations no longer define OKRs for individual contributors as these OKRs tend to look like a task list and lead to conflating OKRs with performance reviews. The motivation for starting OKRs at the company, team, and individual levels was inspired by the 2014 Google Ventures Workshop Recording in which Rick Klau explains that OKRs exist at 3 levels. Subsequently, in November 2017, Klau clarified via twitter: “6- Skip individual OKRs altogether. Especially for younger, smaller companies. They’re redundant. Focus on company- and team-level OKRs.” Additionally, there is criticism that creating OKRs at multiple levels may cause too much of a waterfall approach, something that OKRs in many ways intend to avoid. [20]

Similar frameworks

There is an overlap with other strategic planning frameworks like Objectives, goals, strategies and measures (OGSM) and Hoshin Kanri's X-Matrix. OGSM however explicitly includes "Strategy" as one of its components.

In addition, OKRs overlap with other performance management frameworks, sitting somewhere between performance indicator (KPI) and balanced scorecard. [21]

See also

Related Research Articles

The Capability Maturity Model (CMM) is a development model created in 1986 after a study of data collected from organizations that contracted with the U.S. Department of Defense, who funded the research. The term "maturity" relates to the degree of formality and optimization of processes, from ad hoc practices, to formally defined steps, to managed result metrics, to active optimization of the processes.

Project management is the process of leading the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.

<span class="mw-page-title-main">Andrew Grove</span> American businessman, engineer and author

Andrew Stephen Grove was a Hungarian-American businessman and engineer who served as the third CEO of Intel Corporation. He escaped from the Hungarian People's Republic during the 1956 revolution at the age of 20 and moved to the United States, where he finished his education. He was the third employee and eventual third CEO of Intel, transforming the company into the world's largest semiconductor company.

Strategic planning is an organization's process of defining its strategy or direction, and making decisions on allocating its resources to attain strategic goals.

A marketing plan is a plan created to accomplish specific marketing objectives, outlining a company's advertising and marketing efforts for a given period, describing the current marketing position of a business, and discussing the target market and marketing mix to be used to achieve marketing goals.

Management by objectives (MBO), also known as management by planning (MBP), was first popularized by Peter Drucker in his 1954 book The Practice of Management. Management by objectives is the process of defining specific objectives within an organization that management can convey to organization members, then deciding how to achieve each objective in sequence. This process allows managers to take work that needs to be done one step at a time to allow for a calm, yet productive work environment. In this system of management, individual goals are synchronized with the goals of the organization.

<span class="mw-page-title-main">SMART criteria</span> Mnemonic, giving criteria to guide in the setting of objectives

S.M.A.R.T. is an acronym used as a mnemonic device to establish criteria for effective goal-setting and objective development. This framework is commonly applied in various fields, including project management, employee performance management, and personal development. The term was first proposed by George T. Doran in the November 1981 issue of 'Management Review', where he advocated for setting objectives that are Specific, Measurable, Assignable, Realistic, and Time-bound—hence the acronym S.M.A.R.T.

A service-level agreement (SLA) is an agreement between a service provider and a customer. Particular aspects of the service – quality, availability, responsibilities – are agreed between the service provider and the service user. The most common component of an SLA is that the services should be provided to the customer as agreed upon in the contract. As an example, Internet service providers and telcos will commonly include service level agreements within the terms of their contracts with customers to define the level(s) of service being sold in plain language terms. In this case, the SLA will typically have a technical definition of mean time between failures (MTBF), mean time to repair or mean time to recovery (MTTR); identifying which party is responsible for reporting faults or paying fees; responsibility for various data rates; throughput; jitter; or similar measurable details.

<span class="mw-page-title-main">Christina Wodtke</span> American product designer (born 1966)

Christina R. Wodtke is an American businessperson and specialist in the area of design thinking, information architecture and Management Science She is currently a lecturer in HCI at Stanford University.

A service-level objective (SLO), as per the O'Reilly Site Reliability Engineering book, is a "target value or range of values for a service level that is measured by an SLI." An SLO is a key element of a service-level agreement (SLA) between a service provider and a customer. SLOs are agreed upon as a means of measuring the performance of the service provider and are outlined as a way of avoiding disputes between the two parties based on misunderstanding.

<span class="mw-page-title-main">Performance indicator</span> Measurement that evaluates the success of an organization

A performance indicator or key performance indicator (KPI) is a type of performance measurement. KPIs evaluate the success of an organization or of a particular activity in which it engages. KPIs provide a focus for strategic and operational improvement, create an analytical basis for decision making and help focus attention on what matters most.

A business case captures the reasoning for initiating a project or task. Many projects, but not all, are initiated by using a business case. It is often presented in a well-structured written document, but may also come in the form of a short verbal agreement or presentation. The logic of the business case is that, whenever resources such as money or effort are consumed, they should be in support of a specific business need. An example could be that a software upgrade might improve system performance, but the "business case" is that better performance would improve customer satisfaction, require less task processing time, or reduce system maintenance costs. A compelling business case adequately captures both the quantifiable and non-quantifiable characteristics of a proposed project. According to the Project Management Institute, a business case is a "value proposition for a proposed project that may include financial and nonfinancial benefit."

The Logical Framework Approach (LFA) is a methodology mainly used for designing, monitoring, and evaluating international development projects. Variations of this tool are known as Goal Oriented Project Planning (GOPP) or Objectives Oriented Project Planning (OOPP).

<span class="mw-page-title-main">Workforce productivity</span> Concept in economics

Workforce productivity is the amount of goods and services that a group of workers produce in a given amount of time. It is one of several types of productivity that economists measure. Workforce productivity, often referred to as labor productivity, is a measure for an organisation or company, a process, an industry, or a country.

Strategic communication can mean either communicating a concept, a process, or data that satisfies a long-term strategic goal of an organization by allowing facilitation of advanced planning, or communicating over long distances usually using international telecommunications or dedicated global network assets to coordinate actions and activities of operationally significant commercial, non-commercial and military business or combat and logistic subunits. It can also mean the related function within an organization, which handles internal and external communication processes. Strategic communication can also be used for political warfare.

Risk IT Framework, published in 2009 by ISACA, provides an end-to-end, comprehensive view of all risks related to the use of information technology (IT) and a similarly thorough treatment of risk management, from the tone and culture at the top to operational issues. It is the result of a work group composed of industry experts and academics from different nations, from organizations such as Ernst & Young, IBM, PricewaterhouseCoopers, Risk Management Insight, Swiss Life, and KPMG.

In organizational theory, organizational analysis or industrial analysis is the process of reviewing the development, work environment, personnel, and operation of a business or another type of association. This review is often performed in response to crisis, but may also be carried out as part of a demonstration project, in the process of taking a program to scale, or in the course of regular operations. Conducting a periodic detailed organizational analysis can be a useful way for management to identify problems or inefficiencies that have arisen in the organization but have yet to be addressed, and develop strategies for resolving them.

<span class="mw-page-title-main">OGSM</span> Goal setting and action plan framework

Objectives, goals, strategies and measures (OGSM) is a goal setting and action plan framework used in strategic planning. It is used by organizations, departments, teams and sometimes program managers to define and track measurable goals and actions to achieve an objective. Documenting your goals, strategies and actions all on one page gives insights that can be missing with other frameworks. It defines the measures that will be followed to ensure that goals are met and helps groups work together toward common objectives, across functions, geographical distance and throughout the organization. OGSM’s origins can be traced back to Japan in the 1950s, stemming from the process and strategy work developed during the Occupation of Japan in the post-World War II period. It has since been adopted by many Fortune 500 companies. In particular, Procter & Gamble uses the process to align the direction of their multinational corporation around the globe.

Innovation management measurement helps companies in understanding the current status of their innovation capabilities and practices. Throughout this control areas of strength and weakness are identified and the organizations get a clue where they have to concentrate on to maximize the future success of their innovation procedures. Furthermore, the measurement of innovation assists firms in fostering an innovation culture within the organization and in spreading the awareness of the importance of innovation. It also discloses the restrictions for creativity and opportunity for innovation. Because of all these arguments it is very important to measure the degree of innovation in the company, also in comparison with other companies. On the other hand, firms have to be careful not to misapply the wrong metrics, because they could threaten innovation and influence thinking in the wrong way.

High Output Management is a 1983 book by Andy Grove, CEO of Intel. It describes many of the management and productivity concepts that Grove used at Intel, such as the objectives and key results (OKR).

References

  1. ↑ Bas, Andriy. "A History of Objectives and Key Results (OKRs)". Plai. Archived from the original on 29 August 2022. Retrieved 29 August 2022.
  2. ↑ Wodtke, Christina (2016). Introduction to OKRs. O’Reilly Media, Inc. ISBN   9781491960271.
  3. 1 2 "What is an OKR? Definition and examples". What Matters. Archived from the original on 24 August 2021. Retrieved 24 August 2021.
  4. ↑ Maasik, Alexander. Step by Step Guide to OKRs. Amazon Digital Services LLC.
  5. ↑ Bas, Andriy. "A History of Objectives and Key Results (OKRs)". Plai. Archived from the original on 29 August 2022. Retrieved 29 August 2022.
  6. ↑ Grove, Andrew (1983). High Output Management . Random House. ISBN   0394532341.
  7. 1 2 3 4 5 Doerr, John (2018). Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs. Penguin Publishing Group. p. 31. ISBN   9780525536239.
  8. ↑ Levy, Steven (2011). In The Plex: How Google Thinks, Works, and Shapes Our Lives . Simon & Schuster. pp. 162–3. ISBN   978-1-4165-9658-5.
  9. ↑ "OKR Cycle". Enterprise Gamification. 18 October 2017. Archived from the original on 8 February 2021. Retrieved 14 August 2019.
  10. ↑ "OKR Case Studies & Stories - Learn from the best who have had success". ZOKRI . Retrieved 13 July 2021.
  11. ↑ Wagner, Kurt (27 July 2015). "Following Frat Party, Twitter's Jack Dorsey Vows to Make Diversity a Company Goal". recode. Vox Media, Inc. Archived from the original on 8 February 2021. Retrieved 3 November 2015.
  12. ↑ Fowler, Susan. "Reflecting On One Very, Very Strange Year At Uber". Susan Fowler Blog. Susan Fowler. Archived from the original on 20 April 2018. Retrieved 19 April 2018.
  13. ↑ Chadda, Sandeep. "6 things I learnt about OKRs @ Microsoft". Medium. Archived from the original on 8 February 2021. Retrieved 9 September 2020.
  14. ↑ "GitLab: Objectives and Key Results (OKRs)". GitLab. Archived from the original on 25 February 2022. Retrieved 25 February 2022.
  15. ↑ "OKRs are not "BAU"". What Matters. Archived from the original on 13 August 2021. Retrieved 24 August 2021.
  16. ↑ "re:Work - Guide: Set goals with OKRs". rework.withgoogle.com. Archived from the original on 19 November 2021. Retrieved 24 August 2021.
  17. ↑ "Going from Good to Better Part 2". What Matters. Archived from the original on 13 August 2021. Retrieved 24 August 2021.
  18. ↑ Lamorte, Ben (29 October 2020). "5 mantras for OKRs coaches". The OKRs Blog. Ben Lamorte. Archived from the original on 8 September 2022. Retrieved 8 September 2022.
  19. ↑ Wodtke, Christina (16 February 2014). "Monday Commitments and Friday Wins". Elegant Hack. Retrieved 6 March 2024.
  20. ↑ Formgren, Johan (15 October 2018). "Power of making a difference at work – Blog Article". Its in the Node. Archived from the original on 8 February 2021. Retrieved 15 October 2018.
  21. ↑ Davies, Rob (9 October 2018). "OKR vs Balanced Scorecard – Paul Niven Explains the Difference". Perdoo GmbH. Archived from the original on 8 February 2021. Retrieved 3 December 2018.

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.