Objectives and Key Results OKR

OKR and MBO are central instruments for achieving management success.

Ideas are simple, implementation is everything! This is the mantra of John Doerr, the consultant of Google and other successful companies who introduced the OKR system and sees it as the basis for sensational success in development and results (see: J. Doerr, OKR Objectives & Key Results, 2017).

Ideas are simple, implementation is everything! OKR

In his book, Doerr uses numerous real examples from global corporations as well as small companies to demonstrate that consistent goal orientation is an indispensable key to sustainable success.
The concept of leading with goals is not new. Peter Drucker already laid the foundation for this approach in his publication “The Practice of Management” as early as 1954. George Odiorne described the theoretical concept of Management by Objectives (MBO) and concretized the practical implementation in “The Human Side of Management (1987)”. It seems important to us that Odiorne recognized that the successful application of the MBO system only occurs when objectives are not set by a superior but are transformed into a cross-hierarchical agreement on objectives. Doerr came to the same conclusions (OKR Objectives and Key Results, p. 10).

According to Doerr, an objective determines the “what?”. Objectives should be aggressive and yet realistic, tangible and unmistakable. Their achievement should represent a clear added value for the organization (cf. ibid., p. 226). The SMART formula attributed to P. Drucker (specific, measurable, actively influenceable, realistic and terminated) means almost the same in terms of content.
Key Results express milestones with the associated results. The latter must be measurable, be it with key figures or with documented results (OKR, p. 226).

Management by agreeing on objectives has been an integral part of our management control systematics for years. We are therefore very pleased that Doerr, with his examples from the practice of successful companies, brings two elements to the fore: The objectives must be agreed upon so that the results to be achieved by the individual actors fit in with the overall objectives of the organization and each objective must be defined in a measurable or at least verifiable form. Every manager will confirm from his experience that finding objectives is relatively easy, but realizing them is very exhausting.
In our opinion, objectives, their metrics and the results achieved should be documented in the management control system. Google even goes so far as to allow every employee to see all objectives, including those of his colleagues, bosses and even the executives.
Management by agreeing on objectives is completely interwoven with the management cycle in the integrated management system, since the latter also serves to determine the results and to look for corrective measures if a goal has not been fully achieved. In the various planning or management levels (corporate policy, strategy, operational management) it is also necessary to agree on objectives, to provide the necessary resources and, in accordance with the management cycle, to analyze whether the intentions have become results.
These interrelationships are consequently also determinants for the design of the management control system.

Management Cycle

The Management Cycle Determines the Value Types

Every manager, whether group leader or CEO, follows the management cycle. He has to plan his area of responsibility. The results they need to achieve must be agreed as objectives with their boss and their own employees in terms of content and deadlines. This requires that target content and target levels be coordinated with the capacities to be provided (people, equipment, money) and with the available knowledge (know how). If investments, process improvements or training are necessary to achieve the objectives, the necessary funds must be budgeted and released. Insofar as project orders are to be provided for this purpose, these must also be planned.

Agreeing on objectives and planning therefore take place in parallel. Their mutual coordination is the prerequisite for the budget resolution (1 + 2).

Management Cycle
Management Cycle

Plan implementation can be “disturbed” by various internal and external influences. For this reason, the actual results must be measured periodically (3) and compared with the objectives and the plans. This is done in a  plan to actual comparison (4). The purpose of this comparison is to find and implement corrective actions (5) which will enable improved achievement of objectives in the next reporting periods.

The integrated planning and control system (IPAC) must be able to map this generally valid management cycle. For this purpose, four value types must be stored in the system:

Plan, actual, variance, forecast (expectation).

Each manager should be able to recognize how well he has succeeded in achieving the plan in his area and what variances have occurred. Starting from the variances he considers which corrective measures could lead to achieving the original plan (and thus also the goal) in subsequent periods.  The monitoring process therefore involves not only identifying variances, but also deciding on and implementing corrective measures.

The forecast helps in the management process to assess whether the corrections decided upon will be sufficient to achieve the agreed objectives by the end of the year or project, or whether further measures, possibly in other areas, need to be introduced. It is important to start from the expected effects of the corrective measures when preparing forecasts and not simply extrapolate planned or actual values from previous periods.

Variances in value between planned and actual figures may also be due to the fact that more or less work was produced in a period than planned. In such cases, the responsible manager rightly demands that actual costs be compared with the planned costs of the work actually performed, not with the original planned values. This requires using flexible budgeting in the management accounting system.

Given the requirements resulting from the generally applicable management cycle, management accounting systems adequate for decision-making must be designed in such a way that they:

    • can present plan and actual figures in quantities, activities and values,
    • enable target to actual comparison by valuing actual activities at planned cost rates (“should-be costs”) and comparing them with actual costs,
    • enable each manager to enter into the system expected activities and values in his area (usually cost center) for the rest of the planning year or project in order to quantify his expectations (forecast).

From the management cycle It can also be derived that in the plans as well as in the actual analysis, only those items need to be listed that the responsible manager can directly influence and therefore be responsible for. The management accounting system should therefore not allocate fixed costs to cost centers or products if the receiver cannot personally determine the quantity and the content of the service on which the allocation is based (i.e., there should be no fixed cost allocation).