OKRs aren't just another dashboard. When used effectively, they help teams make decisions, focus their energy, and align the organization's priorities with their day-to-day work.
For a manager, the challenge isn’t just about writing well-crafted objectives. It’s about setting a clear direction, clarifying expected results, and fostering conversations that will enable the team to adjust its actions.
The OKR method provides a framework for achieving this. It distinguishes between the goals to be achieved and the results that will be used to measure progress. It also gives managers a tool for discussing priorities, trade-offs, and challenges encountered.
A useful OKR does not replace management. It makes management clearer, more collaborative, and more action-oriented.
The OKR method links a goal, measurable results, and a monitoring cycle. It helps a team understand where it wants to go, how it will measure its progress, and what decisions will need to be made along the way. OKR stands for Objectives and Key Results. The method therefore distinguishes between two complementary elements.
The objective describes the direction to take. It must be clear, inspiring, and ambitious enough to give meaning to the work. The key results then indicate how to measure progress toward that objective.
An OKR thus answers two questions:
The objective remains qualitative. Key results provide the metrics. This distinction prevents the objective from becoming merely an indicator or a to-do list. The method does not replace performance management. Rather, it provides a framework for aligning priorities, tracking results, and making trade-offs.
To understand the difference between OKRs and overall performance management, see Performance Management: Engaging Without Demotivating.
An OKR goal should provide clear direction without specifying every action to be taken. It articulates an ambition for a given period and helps the team understand the desired change.
Start by identifying the priority for this period. The right question isn't just "What do we need to do?", but rather, "What change do we want to achieve in the coming months?"
The objective must then be linked to the organization’s priorities. This connection helps the team understand why the topic matters and how their contribution fits into the bigger picture.
A useful goal is usually:
Avoid overly general phrases such as “improve marketing” or “increase customer satisfaction.” They do not yet provide a sufficiently specific direction.
Choose wording that conveys a transformation. Example: “Make client meetings more valuable for clients and more effective for salespeople.”
The objective does not yet specify all the means to be used. It sets forth a shared goal, which the key results will then make measurable.
The OKR method requires making choices, because a team cannot focus its energy on all priorities at the same time. If it sets too many objectives, it risks spreading its efforts too thin and turning every issue into an emergency.
To start, select two or three key objectives for the period. They should be areas where the team can actually make a difference.
Before finalizing a goal, ask yourself a few questions:
This last question is crucial. A goal should not be added to the list of priorities without requiring trade-offs in terms of the schedule, resources, or division of labor.
A useful OKR also involves making trade-offs. It helps the team identify what will not be addressed at this time, in order to maintain the quality of the work on the selected topics.
A key result measures an achieved outcome, not simply an activity that has been carried out. It should make it possible to determine whether the team is getting closer to its goal.
Let's go back to the example of client meetings. Key results might include:
These key results are not actions. “Review marketing materials” or “organize three workshops” describes an activity. This activity may contribute to the OKR, but it does not directly measure the result achieved.
A key result should be able to complete the following sentence: “We will know we have achieved the objective if, at the end of the period…” The answer must be observable and specific enough to allow for discussion.
To check the quality of a key result, ask yourself:
It is also important to distinguish between outcomes that the team can directly influence and those that depend on many factors. A team can influence response times or the quality of a customer journey. However, it does not have sole control over overall revenue.
A number does not automatically make a goal meaningful. It can even create a false sense of precision when the data is difficult to measure or has no direct connection to the team’s actions.
A key result should be quantified when doing so provides useful information. In some cases, an indicator of quality, adoption, or reliability will be more relevant than a volume metric.
It is also important to distinguish between:
Objectives and key results must be based on verifiable information. If you use an example in an article or other material, clearly indicate when it is fictional.
This precaution helps maintain the team’s trust. A goal doesn’t have to be spectacular to be useful. Above all, it should help everyone understand what matters and how progress will be measured.
For a manager, OKRs are primarily used to clarify priorities and facilitate decision-making. They should not be confined to a strategic document that the team rarely consults.
A manager must be able to explain:
This explanation is just as important as the OKR itself. An objective that is understood only by management will not guide day-to-day work.
Communication should remain practical. A team meeting, a one-on-one, or a project debrief can help connect the OKR to real-world situations.
An employee should be able to answer a simple question: “How does my work contribute to advancing this objective?” If the answer remains unclear, the OKR likely needs to be reworded or better aligned with operational priorities.
Each key outcome must have a designated person in charge, without becoming the sole responsibility of a single individual. The person in charge monitors progress, coordinates contributions, and alerts the team when the course needs to be adjusted.
He must be close enough to the subject to understand:
Appointing a leader does not, therefore, mean shifting all responsibility onto that person. OKRs remain a collective commitment. The leader acts as a guide and facilitates coordination.
The team also needs to know who makes the final decision in the event of a dispute. Without this clarification, key results may remain displayed in a tool without actually guiding real-world decisions.
An OKR shouldn't be set at the beginning of the period and then forgotten. It should come up in team discussions and help determine priorities.
Follow-up items may include:
Follow-up isn't about asking whether all tasks have been completed. It's about understanding whether the team is getting closer to the expected result.
A team may have taken many actions without making progress toward its key result. In that case, it should be able to reevaluate its approach, rather than simply adding new tasks mechanically.
The frequency depends on the context. Frequent follow-ups may be useful for an operational objective. Less frequent follow-ups may be sufficient for a strategic objective. In any case, these discussions should allow for adjustments to the course of action.
The end of the cycle should not be reduced to a single grade. It should provide an opportunity to understand what the team has learned and to prepare for the next period.
The team can review:
Partially achieving a goal does not automatically mean that the OKR has failed. It is important to understand what the team has learned and whether the goal was appropriately set.
Conversely, a result achieved without difficulty does not always mean that the goal was sufficiently ambitious. The assessment must therefore focus on the quality of the goal, not just on the percentage achieved.
This review may lead to:
Certain practices reduce the effectiveness of the method:
OKRs should support work-related conversations. They do not replace one-on-one discussions, feedback, or decisions made by the manager.
It is also best not to use an OKR as the sole basis for individual performance evaluations. An outcome often depends on several people, external factors, and a changing context.
SMART helps you set a specific, measurable, and time-bound goal. The OKR method provides a broader framework for linking an ambition, key results, responsibilities, and a monitoring cycle.
The two approaches can therefore be complementary. SMART can help clarify certain key results. OKRs then ensure alignment between the team’s priorities and the expected results.
The key is not to choose a method just for the sake of it. The framework you choose should help the team make better decisions, track its progress, and adjust its actions.
OKRs aren't valuable because of the number of tables created or the complexity of the vocabulary used. Their value lies in the conversations they enable and the decisions they facilitate.
For a manager, the method serves primarily to clarify the direction, focus the team’s energy, and make trade-offs more apparent. It helps employees understand what matters, what they can influence, and how their work contributes to a shared goal.
Would you like to help your managers turn a strategic goal into concrete objectives and an action plan? Discover the NUMA’s OKR Action Plan training course.
OKRs aren't just another dashboard. When used effectively, they help teams make decisions, focus their energy, and align the organization's priorities with their day-to-day work.
For a manager, the challenge isn’t just about writing well-crafted objectives. It’s about setting a clear direction, clarifying expected results, and fostering conversations that will enable the team to adjust its actions.
The OKR method provides a framework for achieving this. It distinguishes between the goals to be achieved and the results that will be used to measure progress. It also gives managers a tool for discussing priorities, trade-offs, and challenges encountered.
A useful OKR does not replace management. It makes management clearer, more collaborative, and more action-oriented.
The OKR method links a goal, measurable results, and a monitoring cycle. It helps a team understand where it wants to go, how it will measure its progress, and what decisions will need to be made along the way. OKR stands for Objectives and Key Results. The method therefore distinguishes between two complementary elements.
The objective describes the direction to take. It must be clear, inspiring, and ambitious enough to give meaning to the work. The key results then indicate how to measure progress toward that objective.
An OKR thus answers two questions:
The objective remains qualitative. Key results provide the metrics. This distinction prevents the objective from becoming merely an indicator or a to-do list. The method does not replace performance management. Rather, it provides a framework for aligning priorities, tracking results, and making trade-offs.
To understand the difference between OKRs and overall performance management, see Performance Management: Engaging Without Demotivating.
An OKR goal should provide clear direction without specifying every action to be taken. It articulates an ambition for a given period and helps the team understand the desired change.
Start by identifying the priority for this period. The right question isn't just "What do we need to do?", but rather, "What change do we want to achieve in the coming months?"
The objective must then be linked to the organization’s priorities. This connection helps the team understand why the topic matters and how their contribution fits into the bigger picture.
A useful goal is usually:
Avoid overly general phrases such as “improve marketing” or “increase customer satisfaction.” They do not yet provide a sufficiently specific direction.
Choose wording that conveys a transformation. Example: “Make client meetings more valuable for clients and more effective for salespeople.”
The objective does not yet specify all the means to be used. It sets forth a shared goal, which the key results will then make measurable.
The OKR method requires making choices, because a team cannot focus its energy on all priorities at the same time. If it sets too many objectives, it risks spreading its efforts too thin and turning every issue into an emergency.
To start, select two or three key objectives for the period. They should be areas where the team can actually make a difference.
Before finalizing a goal, ask yourself a few questions:
This last question is crucial. A goal should not be added to the list of priorities without requiring trade-offs in terms of the schedule, resources, or division of labor.
A useful OKR also involves making trade-offs. It helps the team identify what will not be addressed at this time, in order to maintain the quality of the work on the selected topics.
A key result measures an achieved outcome, not simply an activity that has been carried out. It should make it possible to determine whether the team is getting closer to its goal.
Let's go back to the example of client meetings. Key results might include:
These key results are not actions. “Review marketing materials” or “organize three workshops” describes an activity. This activity may contribute to the OKR, but it does not directly measure the result achieved.
A key result should be able to complete the following sentence: “We will know we have achieved the objective if, at the end of the period…” The answer must be observable and specific enough to allow for discussion.
To check the quality of a key result, ask yourself:
It is also important to distinguish between outcomes that the team can directly influence and those that depend on many factors. A team can influence response times or the quality of a customer journey. However, it does not have sole control over overall revenue.
A number does not automatically make a goal meaningful. It can even create a false sense of precision when the data is difficult to measure or has no direct connection to the team’s actions.
A key result should be quantified when doing so provides useful information. In some cases, an indicator of quality, adoption, or reliability will be more relevant than a volume metric.
It is also important to distinguish between:
Objectives and key results must be based on verifiable information. If you use an example in an article or other material, clearly indicate when it is fictional.
This precaution helps maintain the team’s trust. A goal doesn’t have to be spectacular to be useful. Above all, it should help everyone understand what matters and how progress will be measured.
For a manager, OKRs are primarily used to clarify priorities and facilitate decision-making. They should not be confined to a strategic document that the team rarely consults.
A manager must be able to explain:
This explanation is just as important as the OKR itself. An objective that is understood only by management will not guide day-to-day work.
Communication should remain practical. A team meeting, a one-on-one, or a project debrief can help connect the OKR to real-world situations.
An employee should be able to answer a simple question: “How does my work contribute to advancing this objective?” If the answer remains unclear, the OKR likely needs to be reworded or better aligned with operational priorities.
Each key outcome must have a designated person in charge, without becoming the sole responsibility of a single individual. The person in charge monitors progress, coordinates contributions, and alerts the team when the course needs to be adjusted.
He must be close enough to the subject to understand:
Appointing a leader does not, therefore, mean shifting all responsibility onto that person. OKRs remain a collective commitment. The leader acts as a guide and facilitates coordination.
The team also needs to know who makes the final decision in the event of a dispute. Without this clarification, key results may remain displayed in a tool without actually guiding real-world decisions.
An OKR shouldn't be set at the beginning of the period and then forgotten. It should come up in team discussions and help determine priorities.
Follow-up items may include:
Follow-up isn't about asking whether all tasks have been completed. It's about understanding whether the team is getting closer to the expected result.
A team may have taken many actions without making progress toward its key result. In that case, it should be able to reevaluate its approach, rather than simply adding new tasks mechanically.
The frequency depends on the context. Frequent follow-ups may be useful for an operational objective. Less frequent follow-ups may be sufficient for a strategic objective. In any case, these discussions should allow for adjustments to the course of action.
The end of the cycle should not be reduced to a single grade. It should provide an opportunity to understand what the team has learned and to prepare for the next period.
The team can review:
Partially achieving a goal does not automatically mean that the OKR has failed. It is important to understand what the team has learned and whether the goal was appropriately set.
Conversely, a result achieved without difficulty does not always mean that the goal was sufficiently ambitious. The assessment must therefore focus on the quality of the goal, not just on the percentage achieved.
This review may lead to:
Certain practices reduce the effectiveness of the method:
OKRs should support work-related conversations. They do not replace one-on-one discussions, feedback, or decisions made by the manager.
It is also best not to use an OKR as the sole basis for individual performance evaluations. An outcome often depends on several people, external factors, and a changing context.
SMART helps you set a specific, measurable, and time-bound goal. The OKR method provides a broader framework for linking an ambition, key results, responsibilities, and a monitoring cycle.
The two approaches can therefore be complementary. SMART can help clarify certain key results. OKRs then ensure alignment between the team’s priorities and the expected results.
The key is not to choose a method just for the sake of it. The framework you choose should help the team make better decisions, track its progress, and adjust its actions.
OKRs aren't valuable because of the number of tables created or the complexity of the vocabulary used. Their value lies in the conversations they enable and the decisions they facilitate.
For a manager, the method serves primarily to clarify the direction, focus the team’s energy, and make trade-offs more apparent. It helps employees understand what matters, what they can influence, and how their work contributes to a shared goal.
Would you like to help your managers turn a strategic goal into concrete objectives and an action plan? Discover the NUMA’s OKR Action Plan training course.
OKRs, for Objectives and Key Results, are a method of managing objectives that enable companies to define and monitor their strategic goals in a clear and measurable way. Objectives represent the results the company wishes to achieve, while Key Results are specific, quantifiable measures that indicate whether these objectives have been met.
To effectively define your Objectives and Key Results (OKRs), start by clarifying your company's main objective and identifying priority areas. Formulate specific objectives, accompanied by tangible measures to evaluate their success. Involve your team members in the process, and review your OKRs regularly to stay aligned with your strategic objectives and react to market changes.
OKRs are a goal management tool that provide clarity and alignment within teams. They enable efforts to be focused on strategic priorities, progress to be tracked using tangible measures, and objectives to be adjusted in response to changes. By motivating teams and empowering them, OKRs promote optimal performance and increased agility.
Discover all our courses and workshops to address the most critical management and leadership challenges.