What is OKR?
OKR stands for Objectives & Key Results. OKR is written in order to clearly see who is in what time frame, which goal to end, which milestone nodes to complete the goal, and which tasks to perform at each node.
Why OKR
The existence of OKR can be regarded as a short-term or long-term life planning of people. For example, if a programmer wants to become a technical director at the age of 35, let’s assume that the key point of his career is: 1: working for 3 years, he needs to become a senior engineer. 2. Work for 5 years to become a senior engineer. 3. Worked as technical director for 8 years. These are the key nodes in the planning and should be completed within the specified time. Then, the specific tasks to complete the nodes are node tasks, such as working for three years to become a senior engineer: 1. 2: Take the time to look at the framework or middleware implementation. These two tasks are the real effort to complete this node. OKR evolved from this to document the development plan of a program.
Which titles make up the OKR
The Key components of OKR are Objectives, Key Results, Action, Who, and Final Time.
How to fill in these titles
Objectives. For example, my objective for this quarter is “Service transformation and upgrading”. It is a broad objective that does not include what you need to do. Next is the Key Results. The title will write these Key nodes in the end goal. For example, the goal of “service transformation and upgrade” is assumed to be divided into three nodes: KR1: Separate xx-related parts and xx-related parts of XX services based on services. KR2: Upgrade each service architecture version to strengthen system XX capability and ensure service stability without dirty data caused by XX. KR3: The landing XX service is decoupled from the XX component. The three KRS written here are all key nodes. If they are completed one by one, it means that the goal has been completed. The title of KR1 is the node that performs the Action, but the specific things that KR1 does are specified in the Action. Note that Who and Final Time are corresponding to the Action. They note the execution of each task by whom and at what point. For example, in KR1 just now, ACT1 is “combing relevant content boundary with XXX”, the person in charge is XXX, and the end time is xxxx-XX-XX. The existence of Action can see the progress status of the target in the most fine-grained manner over time, and can better judge the risk of the target through the execution status, so as to facilitate the discovery of problems.
