What are the Potential Problems of Implementing OKRs in an Organization?

Or “What are the problems with implementing metrics in an organization?”

OKRs are another form of the use of metrics in an organization with the aim of improving results delivered to the business. Metrics fall under the general category of “bureaucracy” that an organization uses in order to ensure the expected outcomes of an organization are routinely achieved.

Bureaucracy is, in and of itself, not necessarily evil, although many treat it that way. In reality bureaucracy is required in order to coordinate, align, and replicate the activities of organizations; the larger and more diverse the organization, the more bureaucracy. What is evil is bureaucracy that appears useless, arbitrary, and capricious. Raise your hand if you have been the victim of processes that seem overly complicated, or metrics that don’t make sense, or spent your time working around something that gets in the way of doing what is right. These are examples of bureaucracy that has outlived its purpose.

Properly done metrics in the bureaucracy produces results for an organization. OKRs are similar. OKRs can produce results for an organization. In order to ensure we understand how to successfully apply this form of bureaucracy, we need to understand potential problems so we can ensure our implementation addresses them. Before implementing, or as you run pilots, you need to ask yourself:

“Is the juice worth the squeeze?”

Potential problems associated with metrics include:

None of this says that OKRs are “bad.” OKRs were designed to address a number of issues associated with the traditional application of metrics (KPI’s, scorecards, etc.) For this reason you are seeing a lot of discussions around OKRs.

But since OKRs have numbers associated with them (the key result) they potentially suffer from the same kind of problems the use of any metrics in an organization has. As we implement OKRs, we need to ensure we address potential shortcomings.