A practitioner’s insights: The problems to solve with OKRs and how to do it

InsightsOKRs

Common problems with Objectives within organizations

Consider your current work context: Do you know your individual objectives? Your team objectives? Your company mission? If you are not sure about those three things, it might be worth to read on.

Enabling an organization to push forward to a shared objective can be quite challenging. In “traditional”, hierarchical organized companies this challenge is solved by a pyramid of objectives that are defined once a year: From company mission to department objectives to team objectives down to the individual employee. The achievement of one or more objectives is often bound to a financial bonus. Once a year, management defines the strategic objective for the company, brakes these down into chunks for middle-management, which itself create the team and individual objectives. Often, progress and feedback on that objectives are only reviewed once a year — in the annual performance appraisals.

This leads to some problems.

Less focus

Thus you break the company objective down to individual, manageable objectives, those objectives can become very incremental and fuzzy. Employees do not relate any more to the overall company mission and only the top level hierarchies “feel” the mission. The organization consists of individuals with different, not related objectives. Consequently, the company’s focus is everywhere and yet nowhere.

Given the 12-month rhythm of performance appraisals, I’ve seen employees working 9 month on their “own” objectives and 3 month on the company objectives. Typically, some month before the cycle ends, employees remember the agreements made with their boss and try to get the score to 100 %. What do they do in the other months?

Less collaboration

Typically, you found a company, when the combination of different skills is necessary and more workforce enables you to reach your objective faster than an individual could. In short: It’s about collaboration of humans.

Different objectives on an individual or department level topped with financial bonus can foster something completely different that collaboration: Employees do not work together and support the company’s objective — instead they try everything to protect their “resources” to reach their own individual objectives. Selfishness or teamishness rules.

Lack of responsiveness

As a consequence of rigid objectives and a long lasting process of objective definition and communication, the organization cannot adapt quickly to new opportunities. Because a new opportunity needs to be communicated to top management and flow down again. A 12-month objective definition process simply seems a bit too rigid for some industries.

Less autonomy

I very much like Daniel Pinks teaching on motivation: According to his research, three factors increase or decrease the motivation of an employee: autonomy, mastery and purpose. If you believe that every employee needs to contribute in order to create a successful product, motivation should be on the top of the list.

With the right implementation of company objectives, you tackle primarily autonomy and purpose. In my experience, mastery develops out of practices and exchange between employees.

It takes courage for senior managers to step back and let the teams do their work. And middle managers, product owners or team leads needs to show backbone to protect teams against micro-management arising from senior management.

Learnings from real life

In the second part of this article, I want to focus on critical features within an organization that make or break the success of OKRs.

Communicate the company mission

Because every team objective depends on the overall company mission, the management’s focus should lay on communicating this objective and making sure that everybody is on the same page. If one employee has vital doubts on the objective, this needs focus. The aim is not to force her to align to the company’s objective, but to go into a conversation. However, it’s every employee’s task to speak up and make him heard. Plan time for this and make sure everybody is heard.

Have an eye on team interfaces

You can also use OKRs as a weapon of selfishness and teamishness. If your team lays back in its key results, it possibly doesn’t support you any more with your daily business requests. I saw that happen.

One solution could be to involve teams into objective and team setting and let the organization adapt from that.

Ditch financial incentives on personal Objectives

There are so many studies on that topic that this incentives are counterproductive. Here’s one example.

Plan time for inspection

If the OKR team score is low and the team didn’t come closer towards the objective, it’s important to plan time for inspection. What have we learned? What did us prevent from doing better? How can we improve next time?

My experience is: If you don’t take the time to step back and come up with new solutions you will do more of the wrong things in the next OKR iteration.

Responsibility for teams

Most teams (I know) want to be responsible for their work. There might be several reasons why a team couldn’t achieve its objective: Maybe the team setup wasn’t right, the market changed, the objective was too ambitious (so you should have reached some success nonetheless) or the team decided wrong. Nevertheless, the team needs time to reflect and iterate.

The feeling that nothing happens after “failing” to achieve the objective is corrosive. After a short while, the team won’t strive for success because there’s no sense of accountability or responsibility. You disengage from reality.

Plan support for teams

It’s crucial to support the teams when defining their (first) set of OKR. Creating key results which can be measured and are actionable is tough — at least the first time. Support from (agile) coaches can be very helpful.

My Conclusion

As well as with all organizational changes, the success depends on the kind of implementation. Start small, let one team perform at least one OKR iteration and protect that team. If the team performs, it will radiate the idea towards other teams. If you sense the pull of other teams, offer them OKRs, too.

Personally, I really like the autonomy, focus and energy that OKRs bring along. Working with motivated individuals striving towards one ambitious objective is simply great.

Workpath Magazine Header

Subscribe to our newsletter to get exclusive content and insights every week.
Subscribe to Newsletter