A design pattern is a general repeatable solution to a commonly occurring problem. In the context of OKR (Objective & Key Results) many companies fail at the implementation stage as to how to arrange the OKR’s in a way that can lead to successful implementation and adoption of the framework.
This challenge will come to you when you have understood the basics of OKR and probably have read a couple of books and articles on the subjective. When implementing the OKR in your company, you need to remember that the organization is not made of different parts and pieces but it’s a complex adaptive system. And this system is run by people who have different motives and need to be satisfied at gut, mind and heart level. Any change we bring into the system needs to be carefully thought through.
The question here we are trying to answer is how you will arrange the OKR’s in your hierarchical complex system. There are 4 basic design patterns which can be applied to implement OKR’s
- Silo Pattern
- Team-based OKR Pattern
- Top-to-bottom flow pattern
- Top-3-level flow pattern
1. Silo Pattern: Each individual owns the objective and all the keys results are owned by the objective owner herself. Its simple to implement and easy to modify but again encourages silos in the company.
2. Team-Based OKR Pattern: Its different from silo pattern in a way that the Key Result are either owned by (a) objective owner reports(team members working under objective manager). Or the Key Result are owned by someone else working under a different manager, but working with the Objective owner to achieve that Objective.
3. Top-to-bottom Cascade Pattern: In explaining this pattern (which means a way to arrange OKR’s) I am assuming that your company has 4 level hierarchy. This OKR design pattern connects the top level execution agenda with the bottom level execution. This means that the agenda of execution is cascaded down till the last mile of the company. But it also assumes that most of the execution is taken care by the bottom layer of the company.
4. Top-3-level Cascade Pattern: Again assuming that your company has 4 level hierarchy. In this OKR pattern, we connect top 3 levels of the company and cascading stops at the 3rd level of the company. And the 4th level will have their OKR’s based on silo pattern. It is based on the understanding that if the top 3 levels of the company are in sync then we will have a better flow of the agenda.
If you are struggling to implement the OKR successfully, we will be happy to have a conversation with you and help you in achieving success in OKR implementation. Feel free to drop mail talk[at]qilotech[dot]com