OKR

An OKR goal addresses one thing for a given period. Goals should be short and inspiring. At the company-wide level, several goals can be adopted (the fewer, the better). OKRs don’t describe everything a company or team does. Furthermore, it’s also important to set KPIs.
Key results are a set of metrics that help assess progress toward achieving a goal. Each goal should be assigned 2 to 5 points (outcomes). Results can (and should) be reviewed regularly.

Goal Example: Improve customer satisfaction with the software produced by the company.
Key Results Example:

• Measured by the number of critical bugs related to software quality reported by the customer during UAT (user acceptance testing). KPI: The percentage of critical bugs is less than 20%
• Measured by the number (as low as possible) of free MDs (man days) awarded to the customer as part of the company’s bug fixes. KPI: The percentage of free MDs is less than 1.5% of the project value
• Measured by the number of positive responses to the satisfaction questionnaire conducted during regular meetings with the customer (once per month). KPI: The average satisfaction rating is 4 out of 5 points

Note: Key results should be measured regularly and frequently, so they shouldn’t lag behind the established goal, e.g., “measured by the NPS score conducted after software implementation.”
The actions we take to achieve the goal are not considered key results/outcomes. For the above goal, an action that is not a KR would be, for example: Implementing an NPS – a customer satisfaction rating system.