Every sector, including HR, is rapidly adopting AI in 2024. As of early 2024, about 38% of HR leaders are actively piloting or have already implemented generative AI technologies within their operations, showing a significant increase from 19% in mid-2023. This is in line with another survey where 61% of CHROs planned to invest in AI in 2024.
The COVID-19 crisis has us all struggling to find a proper work-life balance as we work remotely (some of us for the first time) for an indefinite period.
When people who have so far been accustomed to face-to-face interactions are expected to communicate solely over voice and audio calls, unresolved issues can quickly escalate.
Non-verbal cues that signal a person’s intentions and opinions can be easily missed in a virtual environment.
You can minimize negative feelings and confusion by incorporating a regular exchange of feedback into your one on one meetings and conversations.
Read on to find some real-life examples of constructive criticism to help you initiate what is bound to be an uncomfortable conversation with your direct report.
What is constructive criticism?
Constructive criticism is distinct from negative criticism.
It is feedback offered with the intention of improvement, thus including specific suggestions for positive change.
Constructive criticism is most effective when it is timely, actionable, specific, and clear.
Why is constructive criticism necessary?
Constructive criticism is necessary to manage workflow and ensure employee growth and satisfaction.
But, your direct report may feel personally attacked if you frame and deliver your feedback incorrectly.
That’s not what you want!
When feedback is delivered with empathy and patience, your direct reports will respond positively.
In fact, research shows that employees do understand the importance of constructive criticism–and even prefer it to praise and congratulatory comments.
Constructive criticism vs. Destructive criticism
Constructive criticism and Destructive criticism differ in their intentions, delivery, and outcomes. While both types of criticism may highlight an issue or a problem, the approaches taken and the end goals are vastly different.
Constructive criticism aims to promote growth and development. It is delivered with care and respect, focusing on specific behaviors or actions that need improvement. The primary goal of constructive criticism is to help individuals realize their potential, empowering them to make the necessary changes for better performance and personal growth.
Destructive criticism, on the other hand, is intended to belittle, demoralize, or undermine an individual. It often lacks specificity and focuses on the person rather than their behavior. Destructive criticism is frequently vague, poorly timed, and accompanied by negative emotions. It can lead to feelings of inadequacy, decreased motivation, and even resentment in the recipient.
Obnoxious Aggression vs. Ruinous Empathy
Kim Scott, author of Radical Candor, said something similar:
Employees prefer obnoxious aggression to ruinous empathy.
Her simple, yet powerful tool to build effective employee relationships is called ‘radical candor,’ which has two dimensions:
Caring personally
Challenging directly
She developed the following quadrant based on her experiences at the workplace:
Obnoxious aggression and ruinous empathy are both unhelpful for your direct reports.
When you criticize somebody with little or no indication that you care, you’re being obnoxiously aggressive.
Ruinous empathy is the opposite–you care for the person, but you’re scared to provide direct criticism.
If you continue to speak and behave as if nothing is wrong just because you want to spare your direct report’s feelings, nothing is going to change.
In short, it’s not about what we’re saying, it’s about how we’re saying it.
Are you following F.A.S.T?
You can deliver constructive criticism in a variety of ways, each suitable for a given situation or direct report, but all these methods should follow the principle of F.A.S.T.
F = Frequency
A = Accuracy
S = Specificity
T = Timeliness
Frequency:
Not all your direct reports will be alike, so you cannot apply the same management style to everyone. Find out how often each person needs feedback and connect individually as required.
Accuracy:
Trust is the glue that holds teams together, especially those working remotely. Before you offer constructive criticism, take care to ensure that your facts are correct.
Specificity:
You’ll want your advice to be taken seriously and have an impact. Skip the generalizations and quote specific examples.
Follow up with an offer of support to show that you’re invested in the progress of your direct report.
Timeliness:
Perhaps the most important factor of all, sharing constructive criticism as promptly as possible will help you minimize friction and negative feelings.
You don’t want to delay feedback, however harsh, because your direct report will continue with the undesirable behavior and you’ll be frustrated with his poor outcomes.
[elementor-template id=”89725″]
7 tried-and-tested Methods and Examples of Constructive Criticism
Not all of these can be used regularly, and some are more effective than others in certain situations.
1 The 3×3 Method
(Proposed byBert Decker in his book ‘You’ve Got To Be Believed To Be Heard.’)
When to use:
When you need a method to offer (and solicit) continuous feedback from your direct reports, the 3×3 method is most effective.
According to Decker,
Receiving three bits of feedback at a time allows people to make course corrections, like a guided missile, as they keep moving onward and upward.
It involves sharing three strengths and three areas of potential development. Remember, authenticity is key.
You’ll want to keep the feedback succinct and limit the number of items you talk about during one meeting to avoid overwhelming your direct report.
By offering constructive criticism in this way, employees view the feedback as a challenge to improve instead of a strategy to quash their ego.
Real-life example:
Suppose you’re a manager and your direct report has just concluded giving a presentation. You need to help her work on her weaknesses while ensuring she doesn’t think she’s a failure.
You won’t be helping her by saying this:
“The content was fine but you need to put more emotion into your speech. Didn’t you see the audience was getting bored?
And why did you generalize so much in your responses during the Q&A session? It didn’t help your listeners at all.”
Instead, you could use the 3X3 method and talk to her like this:
“The presentation was very well put together. However, it could have been more impactful with a more emotional delivery.
The introduction and closing were especially strong, but a conversational tone would have engaged the audience better.
It was interesting to see how you quoted from a wide variety of sources, but more specific examples in the Q&A session would have been good.”
2 The 5 Word Review Method
(Created by Paul English, CEO of Kayak.com)
When to use:
When you want to offer high-level feedback to your direct reports as you observe trends in their performance and behavior, the 5 Word Review method can get your message across in a non-threatening, relaxed, and friendly manner.
It is a great way to build and strengthen your working relationship with your direct report.
Here’s how it works:
1 Note down 5 words to describe your direct report. (2-3 positive, 2-3 negative)
2 Meet in an informal setting, such as a cafe or over lunch (a one on one meeting would be great!) and look over these words with your direct report. (~1 hour)
3 Discuss each word in detail to understand it fully and generate several perspectives.
Remember not to rush through the positive words to focus on the negative ones.
The positive words should describe what you like about your direct report and what they should continue doing.
Give yourself an hour to discuss the meaning behind each word and ensure that your direct report understands them fully.
The simplicity of the method makes it useful to give feedback at any time in the year. It highlights overarching trends like what your direct report consistently does right or wrong.
Since it feels more like a friendly chat than a harsh feedback session, your direct report is less likely to be defensive and more likely to make good use of your guidance.
Real-life example:
Let’s say one of your direct reports works well as an individual contributor, but less so as a team player. However, the project he is involved in requires him to collaborate with others.
You could give him the following words:
Quick
Technical
Controlling
Conservative
Organized
During the discussion, you can praise his timeliness and his ability to grasp the nuances of a project quickly.
You can appreciate the strength of his technical knowledge.
Next, you can discuss how he’s possessive of his work and unwilling to take risks or think out of the box–which is harming the outcomes of the project he’s working on. Talk about how he can try to be more trusting of his teammates and rely on them to contribute useful ideas.
Lastly, you can say that his organizational skills are helping his team members work smoothly on the project.
3 The Situation, Behavior, Impact (SBI) Method
(Developed by The Center for Creative Leadership)
When to use:
This method of giving constructive criticism is most useful when a situation has come up suddenly and you’re required to offer feedback immediately.
It helps you manage difficult, unexpected situations, and communicate negative messages in a delicate manner.
The steps are:
1 Explain the situation.
2Highlight the specific behavior you’re addressing.
3Describe how this behavior affects you, the team, or the business.
Remember to use “I” statements and keep judgments out of your feedback to prevent undermining your message.
The SBI model helps direct reports understand the impact of their behavior on other people. It gives them a chance to understand your concerns without feeling like a chastised child.
Some other similar models, which are also widely used, are:
1 BEEF (Behavior, Example, Effect, Future)
2 AID (Action, Impact, Development, Desired Behavior)
3 BIFF (Behavior, Impact, Future, Feelings) — adds an additional step at the end to gauge how the individual feels after receiving the feedback
Real-life example:
Imagine you have a direct report, Susan, who is consistently coming late to work.
You don’t want to attack her like this:
“Susan, you’re coming in late every day. If this continues, we’ll have to dock your pay.”
Instead, use the SBI model to say something like this:
“Susan, I want to talk to you about logging in late every day.
When you’re late for your shift, we have to hold someone over from the previous shift.
This requires us to pay that person over time, it causes your co-worker inconvenience, and it may also affect the quality of work if she doesn’t fully understand your job. Do you understand?”
4 Pendleton’s Feedback Model
(Developed by Pendleton in 1984)
This method of giving constructive criticism has most often been used in the medical industry.
Some tech companies like Lucidchart, a web-based proprietary platform that allows users to collaborate on drawing, revising, and sharing charts and diagrams, have successfully employed it as well.
When to use:
When you’re looking to involve your direct report in the feedback and give him a chance at self-reflection, Pendleton’s feedback model is the best.
This method helps you set a positive tone for the feedback session right from the start. The guided self-reflection helps your direct report meet his professional goals successfully.
You can follow these steps:
1Encourage your direct report to describe what he thinks is going well.
2Talk about positive interactions and discuss the factors that lead to good results.
3Describe the areas of improvement and explain what your direct report could have done differently.
Real-life example:
An example of constructive criticism using Pendleton’s feedback model is:
Manager: So David, how do you think things are shaping up with your current project?
Direct report: It has been good so far; just that initially the guidelines were not clear so there was a bit of confusion about which approach we should take.
Manager: Right, now that that has been taken care of, I can see things are going really well. Our client was really happy with the quality of our first submission.
Direct report: I’m glad, and I hope to continue delivering satisfactory quality. My editor has been super helpful with suggesting ways I can make my document better.
Manager: That brings me to a topic I wanted to discuss. Perhaps it would be good if you could block off some time on both your calendars to discuss changes to your document instead of dropping in by her desk every half an hour with queries. Not everybody likes to be interrupted frequently because it prevents them from concentrating on their work.
Direct report: I didn’t realize that. I’ll do so going forward.
5 The Stop, Start, Continue Method
(Developed by Phil Daniels)
When to use:
When you need to coach new team members and familiarize them with the organizational culture, the Stop, Start, Continue method is quite helpful.
This is how you can go about it:
1Discuss things that do not work and the direct report should STOP doing
2Shift focus to new things the DR should try out instead, stating what she should START doing
3End the session by pointing out things the DR is doing right and should CONTINUE doing
The stop, start, continue method is a neat and organized approach to offering constructive criticism.
Real-life example:
Let’s say you have a new direct report who is great at his work but tends to get angry and confrontational during discussions.
You could say something like this:
“When you raise your voice during our meetings whenever somebody contradicts you, you make your team members uncomfortable. This is something you need to be aware of and not do in the future.
What you could do instead is practice flexibility with your ideas. You could discover new approaches by listening to the opinions of others.
In fact, you excel at creating eye-catching presentations with innovative ideas, and I would love to continue seeing that from you.”
6 The STAR – Situation, Task, Action, Result – Method
(Developed by Development Dimensions International Inc.)
When to use:
When you want to give feedback on certain specific actions of your direct report, the STAR feedback model is effective.
This model breaks feedback into 4 categories:
1 Situation/Task: You explain the specific situation or task your direct report was involved in.
2 Action: You describe the action taken by the direct report, including details of what was said and done. The action can be negative or positive.
3 Result: You outline the result of the action taken so that your direct report understands what he did right or wrong.
If your direct report took a negative action, you should talk about an alternative action and its consequences to show what could have been done and how it would have been more effective.
Real-life example:
Let’s say Sarah, one of your direct reports, has a habit of procrastinating and tends to complete her work too close to the deadline. You want to talk about time management with her.
You could go about it like this:
“Sarah, we almost missed our project submission deadline.
I saw you coming in early and staying back late to finish the work just before the end date.
While it’s good that you’re dedicated enough to ensure that you don’t miss the deadline, your delay caused your team members to work overtime, too.
This causes them a lot of inconveniences. Do you understand?”
[elementor-template id=”89725″]
Guide to Giving Constructive Feedback
7 The DESC – Describe, Express, Specify, Consequences – Model
(Developed by Sharon and Gordon Bower, authors of Asserting Yourself)
When to use:
Use the DESC feedback model when you’re stressed about giving constructive criticism to your direct report and you need a structured method to make your method clear.
The steps involved are:
1 Describe: your direct report’s behavior clearly using “I” statements.
2 Express: the impact the behavior had on you, the team, or the company.
3 Specify: what you’d like your direct report to do the next time around.
You can use a directive tone (Next time, when something like this happens, I would like to see….) or a participative tone (How do you think we can avoid something like this in the future?)
Ask your direct report if he agrees to what you’ve said.
4 Consequences: You can make the consequences of the desired behavioral change clear.
Of course, it helps to prepare what you’re going to say beforehand so that no important details are missed.
Real-life example:
Let’s take the example again of a direct report turning up late consistently. A good way to discuss the issue would be:
“Terence, I want to talk to you about your late coming, especially the fact that you have come an hour late three times this week.
When you regularly come in late, it makes the whole team look unprofessional. Also, it sets a bad example for our new team members.
I’d like to see you make an effort to come into work on time every day unless there’s a pressing issue.
You’ll also be able to attend the daily stand-ups if you step in at 9 every day. I hope you understand.”
Pro Tip: Don’t use the Feedback Sandwich method (positive – negative – positive) because it gets predictable and your positive comments lose value if your direct report perceives them to be dishonest.
Employees may even begin to associate positive comments with negative feedback. And you don’t want that!
Use one on one meetings to give constructive criticism
One on one meetings are a powerful way to offer constructive criticism because it is a face to face conversation instead of a written message.
It is also a recurring event in your calendar, a private and psychologically safe space where you and your direct report can talk about things you normally wouldn’t say in a group meeting.
You don’t need to schedule a special meeting to give feedback; since feedback can be a part of the one on one meeting agenda.
The regularity of one on one meetings ensures that you are offering constructive criticism in a timely manner, although not in the heat of the moment (which could be damaging).
Receiving Constructive criticism
Till now we have only talked about how to give constructive criticism, but how do you receive it? It’s hard to accept that someone has pointed out something wrong with your work, especially if the person giving feedback is in a position of authority over you.
It’s human nature to feel a little defensive, especially if you’ve put a lot of work into something. So, how do you take criticism without letting it get under your skin?
Here are some things to keep in mind:
Embrace the opportunity to learn: Understand that receiving constructive criticism is an opportunity to grow and improve your skills. Remind yourself that nobody is perfect, and we all have areas where we can improve. When someone offers feedback, view it as a chance to learn from their perspective and experience.
Focus on comprehension, not rebuttal: As you listen to the constructive criticism being offered, concentrate on understanding the message rather than preparing a response or defending yourself. Keep in mind that the person is sharing their insights to support your development, so approach the conversation with an open mind.
Ask for clarification without disputing the feedback: While it’s not appropriate to contest or deny the feedback, it’s perfectly acceptable to inquire for more information or to brainstorm ways to enhance your performance. If you’re not prepared to ask questions immediately following the feedback session, that’s alright. Schedule a follow-up meeting to discuss strategies for improvement further.
Evaluate the feedback objectively: After receiving the criticism, take some time to objectively evaluate it. Consider the validity of the points raised, and determine if they can help you improve. If the feedback is valid, create a plan to address the areas where you can improve. If it’s not, simply let it go.
Separate the feedback from your self-worth: Remember that constructive criticism is about your work or performance, not about you as a person. Don’t take it personally or let it define your self-worth. Focus on the specific areas that need improvement rather than dwelling on negative feelings.
Conclusion
We hope these examples of constructive criticism will help you speak candidly with your direct reports.
You must take your time choosing the method that best works for you and your direct report.
You can pick a method that suits you best or combine a few methods to arrive at your own unique strategy.
Constructive criticism is a normal and essential part of work.
Make your direct reports look forward to it, if not love it.
FAQs
How do you accept criticism in a real-life situation?
Accepting criticism involves active listening and remaining open-minded. Start by staying calm and avoiding a defensive response. Listen carefully to understand the feedback, ask for clarification if needed, and show appreciation for the input. Reflect on the criticism, consider its validity, and use it as an opportunity for growth and improvement.
What 5 words could you use for constructive criticism?
Constructive criticism can be conveyed using words like “suggestions,” “opportunities,” “improvement,” “feedback,” and “enhancement.” These words emphasize the positive intent of the critique and encourage a growth mindset.
How do you handle criticism at work?
Handling criticism at work involves maintaining professionalism and a receptive attitude. Listen attentively to the feedback without becoming defensive. Ask for specific examples to understand better. Take time to process the criticism, self-reflect, and decide on actionable steps for improvement.
What are the benefits of constructive criticism?
Constructive criticism provides insights into areas for improvement, helping you enhance your skills and performance. It encourages self-awareness and growth by highlighting blind spots. Constructive feedback also fosters better communication and trust among colleagues, contributing to a more collaborative and productive work environment.
What stood out is the deep understanding of the Peoplebox.ai team and their willingness to listen & enhance the platform to scale with our long-term needs.
Khilan Haria
VP and Head of Payments Product, Razorpay
I'm glad that we partnered with Peoplebox.ai for our company-wide OKR rollout. Thanks to its simplicity, we achieved significant adoption within two quarters
Rohit Arumugam
Business Head, Nova Benefits
Since we started using Peoplebox.ai, we have been able to bring all of our leadership across the organization together and show them how all of our goals align
Jaclyn Hoover
Senior Director HR, Propel School
Driving the entire interface through slack is simply brilliant especially for a tech product company! There was zero time spent on training! It can not get easier than that!
Swapna Nair
VP - HR, Khatabook
I chose Peoplebox.ai because it had integrations with the tools we use for sales and engineering to automate updating of key results and sync projects
How to Roll Out OKRs for First Time: 7 Steps Startegy
How to Roll out OKRs for the first time is a question common among organizations just introducing OKRs.
Imagine a scenario-
You are rolling out OKR for the first time.
One thing goes wrong and… Boom!
Your employees are already hating the process- even before it took a pace.
You certainly wouldn’t want that to happen in your organization. OKRs can surcharge and accelerate your organizational growth. But the key is to get this done right.
That’s why a well-planned rollout is significant for the success of an OKR system.
Introduce the new goal-setting approach strategically but not in a mechanical process. Every organization is unique and can face unique challenges while implementing OKRs.
[elementor-template id=”89725″]
How to roll out OKRs: Here are 7 Best Practices for a successful OKR rollout
1 Communicate the OKR Methodology to all the teams
Get everyone in the organization on board with OKRs. Present the concept clearly and precisely. Educate everyone on the OKR language.
While some people will embrace the changes with open arms, there are also going to be some skeptics into the bargain. You must let them express their concerns and provide answers to their “why, how, and what?” questions.
Explain to them the benefits of implementing the OKR framework. Highlight how it’s going to impact the business and the individual success of the employees.
Organize workshops, training, discussions, introductory presentations, and seminars to help your employees’ design quality OKRs. Transparently explain to them the strategic execution, alignment, expectations, and tools they will be required to use for the purpose.
To help everyone speak the same language, document your company OKR framework
2 Inspire with success stories
List the names of reputed companies like Google, Netflix, Intel, LinkedIn, Twitter, etc. which have successfully implemented OKRs. Narrate their success stories to help them visualize how OKRs can cater to their individual success.
For example, OKRs helped LinkedIn become a 20 Billion Company. Jeff Weiner, CEO of LinkedIn, describes OKRs as, “something you want to accomplish over a specific period of time that leans toward a stretch goal rather than a stated plan.
It’s something where you want to create greater urgency, greater mindshare.”
You can either go for an organization-wide rollout Consider running an OKR Pilot first, depending on what fits you best.
If you have a culture that’s open to change and a flexible structure of functioning, an organization-wide rollout will work best for you. But it’s always best to take small steps. Start from one part and gradually move to others.
[elementor-template id=”89725″]
Crafting and implementing OKRs across the entire organization can seem overwhelming especially if you are a large organization. Instead, choose a particular part of the organization and run a pilot project.
“If you concentrate on small, manageable steps you can cross unimaginable distances.”
It’s also important to decide “how often?” will OKRs be reviewed. Will it be done quarterly or annually?
4 Go for the Top-down approach
A top-down approach to OKRs was the first pattern attempted. The top management has a significant role in setting the overall direction of the company. Starting from the top provides clarity for the rest of the organization.
“People buy into the leader before they buy into the vision.”
For example, you can start with the senior leadership team. Make them an example to roll out OKRs to the departmental heads. From there you can move on to team leaders, and to the rest of your teams.
5 Get aligned
You can’t just sit with a blank sheet in front and magically start crafting the perfect OKRs. You need to understand the context. Make the company mission and vision your starting point and tailor your OKRs accordingly.
Buy-ins are critical for OKR success. The success of OKRs depends on the collective effort of each team member. You can imagine it as a group dance performance where everyone needs to perform their parts well to make it a masterpiece.
Thus you need to align the efforts of the workforce, executive leaders, and company heads both horizontally and vertically. This will help you foster transparency, smooth cross-functional communication, and reduce overlap among departments.
6 Track and monitor progress
Tracking OKRs are important to evaluate and measure the progress and understand which teams are falling short.
You can identify any issues and make course corrections as required by Monitoring progress.
Leverage technology to track OKRs. It will make the process transparent.
Using OKR software will also automate the calculations and save your time as you are no longer required to manually update the progress of each team member.
Bonus tip: Remember to celebrate whenever you Hit the nail on the head through OKR win meetings and shoutouts to keep
7 Do frequent check-ins
To stay on top of OKR progress, you need to do regular check-ins. Employees might feel overwhelmed with concerns and doubts, especially in the initial days.
Regular check-ins will give your employees direction. And provide them the required assistance and guidance. Frequent Check-in meetings will also identify the overlappings, increase accountability and ensure execution.
Define your preferred frequency of Check-in meetings. You can do it weekly or monthly as per your organization’s needs. Although weekly check-ins are most recommended to keep track of the progress and evaluate continuously.
Have OKR Champions
Consider having OKR champion who starts implementing the OKR framework with a strong war cry. Build a team of champions who will work as ambassadors to head the change. And make the OKR framework run smoothing across the organization.
They work as mentors and internal OKR experts. And can help you adopt and execute OKRs at all levels of the organization. These OKR enthusiasts will make sure that every concern is addressed, every ‘whys and wherefores’ are explained.
Too many objectives and key results: Less is more. Don’t set more than 5-7 Objectives and 3-5 key results.
Fill it, Forget it: Don’t set OKRs just to forget in a few days.
Mixing KPIs with OKRs: KPIs aren’t a substitution for OKRs. They have separate roles and outcomes.
Rigidity: Rigid adherence to rules can lead to disengagement. Instead, move forward with a flexible and intuitive OKR approach
Link OKRs with Recognition: Don’t make the mistake of making OKRs a base for your reward and recognition program. It can negatively affect performance. And compromises the business output.
The start is never perfect
You might struggle when you are just starting. But after a few OKR cycles, you are sure to hit your stride.
To end, OKR’s success depends on consistency. So, remember to continuously reflect, learn, and refine the process.
Hope we were able to answer all your queries in our blog How to roll out OKRs for the first time? If you have questions feel free to comment below.
Pooja Pooja
Types of OKRs: Aspirational OKRs vs Committed OKRs
Every organization wants to grow, but how do you set goals that are both achievable and visionary? The answer lies in the types of OKRs: committed and aspirational.
Whether it’s near-term performance or long-term innovation for your business, you’ll know just how to leverage the power of committed and aspirational OKRs effectively to unlock new levels of success for your business.
Committed OKRs are about clear, attainable targets that teams can confidently deliver within a set timeframe. This type of OKR delivers accountability and is important for day-to-day business success.
Aspirational OKRs, on the other hand; push teams to be bigger and challenge themselves. The moonshots: ambitious OKRs are meant to stretch an organization from its comfort zone, kindling innovation and long-term growth.
In the rest of this blog, we will take the difference between these two types of OKR apart and see how to balance them in such a way that they enable performance as well as inspiration.
What are Aspirational OKRs and Other Types of OKRs?
A committed OKR is a stretch goal that the team has to achieve or complete before the cycle is over. A committed goal pushes the team to reach, but still achievable attainment. All metrics of the Key Results must be completed fully and on time. Consider a situation like this:
Daniel’s organization and his teams have agreed to execute certain OKRs and have mapped a precise action plan on how they are going to do so.
These are called Committed OKRs.
An aspirational OKR sets the bar for success further out, and by design will exceed a team’s ability to execute in a given quarter. When they set such a high bar as to be seemingly impossible they are called 10x goals, or “moonshots.” While most aspirational OKRs are never fully achieved, they exist to push a team to think bigger than a committed OKR. Consider the following case:
Martha’s organization is more visionary. They have stretched goals. And her teams are not likely to fully achieve these ambitious goals.
These are called Aspirational OKRs.
Understanding the distinction between aspirational and committed goals is crucial for effective goal-setting and team motivation within the OKR framework. Aspirational goals encourage ambitious thinking and long-term vision, while committed goals focus on immediate, measurable outcomes.
Learning OKR focuses on the acquisition of knowledge, new skills, or insights rather than a direct achievement of business outputs. Extremely helpful when entering new areas or uncertainties and requires experimenting, learning, and developing new skills, Learning OKRs distinguish between usual output measuring of success and measuring acquisition of knowledge, that will later add value for future objectives. For example:
Jerry wants to gain a deep understanding of machine learning to drive full product development. He wants to finish three advanced courses and test his skills by building a model in sandbox.
These are called Learning OKRs.
Aspirational OKRs and Committed OKRs: Key differences
When you aim for the stars, you may come up short, but still reach the moon.
– Larry Page
Read on to find out the key difference between Committed OKRs and Aspirational OKRs.
Objective
Aspirational OKRs are meant to push the boundaries and encourage employees to achieve visionary objectives. Committed OKRs, on the other hand, focus on committed objectives that offer a more realistic vision of goals with fully achievable results.
Aim
Committed OKRs help companies achieve their goals through individual and team achievements. Aspirational OKRs are often beyond the current capacities of the organization but help in pushing boundaries.
Timeframe
Aspirational OKRs are usually created to focus on long-term strategic vision while Committed OKRs offer short-term operational priorities to guarantee progress in the short term.
Committed OKRs are supposed to have a 100% success rate as each key result comprises fully achievable targets. Aspirational OKRs are usually found to have a success rate of 60-70%.
Committed and Aspirational OKR examples
The difference between committed and aspirational OKRs is subtle. Committed objectives are meant to be fully achievable, requiring teams to concentrate on straightforward priorities without taking unnecessary risks, ultimately serving as motivational tools to foster small wins and consistent progress.
A standard example in the sales team scenario might be like:
Committed OKR
O: Expand to the US market
KR1: Close first 6 start-ups
KR2: Get a meeting-to-close rate of 6%
KR3: Reach average deal size of $200
Aspirational OKR
O: Capture the entire US market in one quarter
KR1: Get onboard 95% of big customers in the US market to grow over competitors
KR2: Get a meeting-to-close rate of 30%
KR3: Reach average deal size of $2000
In the managerial team, these OKRs can manifest like such:
Committed OKR
O: Improve customer satisfaction with the existing solutions
KR1: Increase customer satisfaction score (CSAT) from 85% to 90% by the end of the quarter.
KR2: Reduce average response time from 15 minutes to 10 minutes within the next three months.
KR3: Train 100% of the support team on the new customer service tools within six weeks.
Aspirational OKR
O: Become the market leader in AI-powered customer service solutions.
KR1: Achieve a 30% market share in the AI customer service industry by the end of next year.
KR2: Launch three groundbreaking AI features that no competitor currently offers within 18 months.
KR3: Secure a partnership with at least two top-tier companies by the end of next year.
In a tech context, OKRs like these can come up:
Committed OKR
O: Improve the performance of the app and reliability
KR1: Reduce app crash rate from 2.5% to under 1% within the next quarter.
KR2: Decrease page load times by 30% in six months.
KR3: Fix 100% of the top ten reported bugs within the next two sprints.
Aspirational OKR
O: Revolutionize the user experience of our mobile app.
KR1: Increase daily active users (DAU) by 100% within 12 months.
KR2: Develop and launch a fully AI-driven recommendation system that personalizes the user experience by the end of the year.
KR3: Achieve a 4.8+ rating across app stores by introducing five innovative features within the next 18 months.
How to decide between Committed OKRs and Aspirational OKRs?
Committed OKRs will work best if your organization is newly introduced to the framework or is still in the rolling-out phase.
With each goal achieved, your team’s motivation and engagement will rise higher. In addition, teams easily get into the habit of running Committed OKRs and make it part of their work culture.
But if you have already used the framework in the past, aspirational OKRs can do wonders for you.
Creating a result-driven work culture takes time. It demands discipline, continuous effort, and a mindset shift of employees and management. So you should start simple and focus on learning the methodology first. And set up the necessary processes to make it work.
Setting aspirational OKRs in the very beginning would make your teams feel overwhelmed and over-pressurized. Extremely ambitious Key Results soon become too much to handle. Learning a new methodology takes time. Once your teams are used to the framework and it becomes a part of their work-life, you can consider aspirational OKRs.
With the later process, you can have objectives and a combination of committed and aspirational key results. While some key results will be easier to achieve, others will aim higher. Understanding the distinction between aspirational and committed goals is crucial for better goal-setting and team motivation.
Choosing the Right Type of OKRs
Choosing the right type of OKRs depends on the organization’s goals, culture, and priorities. Committed OKRs are suitable for organizations that need to achieve specific, measurable outcomes within a set timeframe. They are ideal for teams that require a clear direction and a sense of accountability. Aspirational OKRs, on the other hand, are suitable for organizations that want to drive innovation, creativity, and excellence. They are ideal for teams that want to push the boundaries and strive for something bigger.
When choosing between Committed and Aspirational OKRs, consider the following factors:
What are the organization’s goals and priorities?
What type of culture do we want to foster?
What kind of outcomes do we want to achieve?
What level of risk are we willing to take?
By considering these factors, organizations can choose the right type of OKRs that align with their goals, culture, and priorities. Whether you opt for committed or aspirational OKRs, the key is to ensure that they are aligned with your company aims and internal communication processes, fostering a balanced approach to achieving both immediate and long-term objectives.
How to balance Committed and Aspirational OKRs?
There is no one-size-fits-all answer, but where OKRs are aligned with company strategy, teams are well educated, open communication exists, and performance is reviewed regularly, it will help keep the balance between aspirational and committed OKRs intact.
However, the first step in finding equilibrium between the two forms of OKRs is that there has to be a knowledge of the difference. It needs to be apparent from the outset that everyone involved makes it clear the distinction between the two OKRs.
Teams and employees may have suitable insights that will assist in determining what is realistically achievable (committed) and what is a stretch but possible (aspirational). This can help determine what the balance ratio for the OKRs is going to be.
A very critical element to succeed with OKRs is reviewing and tracking the progress. With weekly check-ins, teams can go through their OKRs regularly and update the same performance data. It becomes easy to track how they have progressed on the outcome of the OKR in the OKR review process.
The grading of OKRs is very clear on the distinction between committed and aspirational goals. Committed OKRs are things to be accomplished within the cycle, and grading is binary: pass or fail. That is, an OKR is said to be successful if 100% of it is accomplished; otherwise, it is regarded as a failure. Aspirational OKRs, on the other hand, are graded along a more nuanced scale.
Common mistakes to avoid while setting up Aspirational OKRs
Here are 6 common mistakes organizations commit while setting up aspirational OKRs-
1️⃣Ignoring organizational structure and needs
A common mistake most organizations commit while writing aspirational OKRs is to write something like, “What can be done more if we have extra resources and luck favors us ?” Instead, you can pretend to be a genie and strive to understand “What our customer needs at present moment?”
2️⃣Unrealistic aspirational OKRs
Aspirational OKRs don’t imply setting unrealistic goals. It should be achievable, with the understanding that your teams won’t have any clue about how to achieve these OKRs. Aspirational OKRs demand overuse of resources. They are fluid and flexible. But still helps your teams focus on well-defined goals.
3️⃣Writing a low-value objective (LVO)
Moving forward with a “Who cares?” attitude is a common pitfall among organizations. Low-value objectives go unnoticed even after the successful completion of the key results.
4️⃣OKRs should be framed to gain tangible benefit
OKRs are a tool for organizations to work for big goals in the long run by breaking them into small chunks that can be achieved within a shorter cycle.
5️⃣A committed OKR must deliver a 1.0
It makes the framework stiff and doesn’t leave scope for improvement.
6️⃣Too many OKRs
How many aspirational OKRs you should set for one cycle will depend on your company’s resources. But never aim for too many Objectives and key results. As it can easily divert your focus altogether.
Best Practices for Implementing OKRs
Implementing OKRs requires a structured approach to ensure success. Here are some best practices to consider:
Align OKRs with company goals: Ensure that OKRs align with the organization’s overall goals and priorities.
Make OKRs specific and measurable: Ensure that OKRs are specific, measurable, achievable, relevant, and time-bound (SMART).
Set ambitious yet achievable goals: Set goals that are challenging yet achievable, and provide a clear direction for the team.
Establish clear key results: Establish clear key results that indicate progress towards achieving the objective.
Track progress regularly: Track progress regularly and provide feedback to teams and individuals.
Foster a culture of transparency and accountability: Foster a culture of transparency and accountability, where teams and individuals are held accountable for their progress.
Provide training and support: Provide training and support to teams and individuals to ensure they understand the OKR framework and how to use it effectively.
Review and adjust OKRs regularly: Review and adjust OKRs regularly to ensure they remain relevant and aligned with the organization’s goals.
By following these best practices, organizations can implement OKRs effectively and achieve their goals. Regularly reviewing and adjusting OKRs ensures that they stay aligned with the evolving needs of the organization, helping teams to maintain focus and drive continuous improvement.
Conclusion
Now that you know the difference between committed and aspirational OKRs and how they can impact your organization’s success, it’s the decision time. Choose the one that will best suit your purpose.
And don’t forget it’s a trial and error method. Have regular OKR check-ins and reviews. Collect feedback during and after each cycle. And use your learnings to avoid further mistakes in the next OKR cycle.
Pooja Pooja
Quarterly OKRs: 5 Tips for Successful Wrap-Up
Imagine a scene! the quarter is about to end and it’s time to review and wrap up quarterly OKRs.
The clock’s ticking. Everyone is in a rush. And you are busy evaluating which goals are yet to be achieved. And what has already been done. It’s also time to think about your priorities for the next quarter.
There are so many checklists and questions going in your head.
Have my teams found ways of closing out quarterly OKRs? Will my teams beat the clock and tick all the boxes? Have they reflected on their OKR progress? How will I deal with this end-of-quarter OKRs rush?
Feeling overwhelmed!!
Here is a step by step guide to help you prepare best to wrap up your quarterly OKRs–
Before you start to review and wrap up quarterly OKRs- remember that wrapping up quarterly OKRs is teamwork. And to see the best results every team irrespective of their department have to come together.
Track your team’s OKR progress and gather the key results scores. You can score your OKRs on a scale of 1 to 10 on the basis of how far the objectives have been achieved.
This will help you evaluate your progress in a truly data-driven manner.
If the scores are low this might suggest that your OKRs were unrealistic. On the other hand, if the score is too high it may suggest that your OKRs were not ambitious enough.
Whatever learning you made from this process. It will help you to form the basis for designing your next set of quarterly OKRs.
Make sure everyone is up to date
It is important to ensure that your teams have clarity about their OKR status. At the same time, they have visibility into what other teams have been doing. It can be achieved through regular check-ins with your teams. Check this ebook on OKR handbook.
This step will help you check if your teams are aligned or not. When everyone in your team is on the same page taking decisions based on priorities becomes easy. As you have the data in hand to rely on instead of guessing.
Organize OKR check-ins
The importance of check-ins for OKR success cannot be emphasized enough. OKR check-ins provide you an opportunity to have 1 on 1 discussion in all OKR matters.
With OKR check-ins you can discuss with your leaders and team members about – what went well, what didn’t work for them, what needs to be dealt with immediately, what problems they are facing etc. at an individual as well as team level.
OKR check-ins will help you understand what’s holding teams back. You will further get the chance to push priorities that might have shifted midway.
Dig into opportunities
Organize Quarterly OKRs review meetings to dig into opportunities. During these meetings, go through each key result with your teams. Find out what went well and what needs to be done better.
Let the OKR leaders from each team present their learnings and achievements before everyone. Here teams can give a small presentation highlighting the most important lessons with context.
So that other teams can benefit from their learnings and experiences. And use them in designing their OKRs for the next quarter.
If you are a large-scale company working with multiple departments. The OKR review meetings can be held at the departmental level.
Plan the future
Now that you have gathered the data and matrix you need through OKR check-ins and OKR review meetings. It’s high time to plan for the next quarter.
OKRs have the power to build the future of your organization. But OKR failures can cost you a fortune.
Hence it’s important to find out the core reasons behind your OKR success or failure for the present quarter. And use it as context while designing OKRs for the next quarter.
[elementor-template id=”89725″]
Do you need to plan new OKRs every quarter?
“Should OKRs change every quarter?” is a question often left unanswered.
Even after an OKR is achieved, you can roll it forward for the next quarter if necessary.
For example, if your OKR was to increase customer satisfaction by 20% in the present quarter. This could be relevant even for the next few quarters.
In case, of missed OKRs, you need to take a call. And decide whether you want to carry it forward or set new OKRs based on the data gathered.
When should you review and wrap up Quarterly OKRs
You should preferably wrap up the quarterly OKRs at least a week prior to the beginning of the next quarter.
But the preparation and discussions for the next quarter should be initiated almost a month before the new quarter begins. This is because designing OKRs takes dedication, time, and effort.
Bonus Tips:
Maintain Transparency from day one. Keep data transparent so that everyone knows how it’s going.
Create a culture of critical feedback. Be honest when it comes to feedback. At the same time be open to getting feedback from your teams as well.
Celebrate wins– even the smallest ones. Recognize your teams for their achievements more often.
Over-communicate. Communication is the key when it comes to wrapping up quarterly OKRs.
Take a moment
Wrapping up end-of-quarter OKRs will allow you to pause and take a moment to think. It provides you time to reflect on your wins, failures, and setbacks. It’s a stitch in time to make sure that your OKR framework is a success.
Follow the steps given to close out quarterly OKRs and make the most out of the process.
