Establishing Annual OKRs For Your Team

Paritosh Aggarwal

Engineering Manager at Airbnb



"I was working with a team that did not conceptually understand what they wanted to achieve long-term. They were very much involved in the day-to-day activities and everyday demand of what needed to get done. There was a lot of focused effort on Sprint planning but with no clear direction or laid out roadmap. As a result, I decided to initiate an annual objective planning scheme."

Actions taken

In short, this meant setting yearly OKRs- which were in addition to the quarterly OKRs. The guidelines for the annual OKRs were as follows:

  • "Inspirational objectives which people could relate to;"
  • "The goals should be ambitious;"
  • "They should also be widely important, for example things that are existential and critical to the success of the team;"
  • "The key results needed to be specific and measurable so that you could grade yourself, or so that anyone could objectively grade how the team performs on those specific measurements."

To establish specific objectives I held a group session with the team and asked them to identify key work streams. Everyone determined their main priorities, the “what’ part of “What is the team doing?” Then I posted a discussion around who was responsible for these things, specifically which teams. I wanted to make sure that we were not going above three or four work streams (or teams) because these would essentially capture the objective portion of the OKR. Ultimately, we landed on three very important goals, or objectives, from this exercise: reliability, platform capabilities, and usability, and from these three goals stemmed out our three major teams.

The next step was to establish the key results (KRs) for these objectives. This process was a bit more difficult because we found it hard to precisely measure how to hit certain KRs. But eventually we managed.

  • "The KR for reliability was the easiest because we wanted to make sure our uptime was above a certain threshold. We had a maximum 1-hour downtime per quarter for our services which led us to come up with a time goal of 99.95%. This is what success would look like the following year if we took out all of the staffing problems and all of the short-term tactical problems. This is what we wanted to achieve."
  • "We knew we wanted to ship two new services as our objective for platform capabilities, therefore we had to launch and enable two new use cases. For both of those two use cases we had key results around adding X new features. As a result, we had KRs for new services, new use cases, and new features, but they were simultaneously all tied together."
  • "The third objective, usability, dealt with having a KR that established an NPS service, a customer satisfaction survey. The survey results should have a base rate of say 4 out 5, for example. Specific and measurable. Additionally, we wanted to enable non-engineers to achieve certain aspects of the product itself without any engineering help, thus the KR would be a self service where people could create 100% of the campaign independently."

I wrote up the OKRs with the three objectives/themes/teams and the key results. The team as a whole felt good about them. It also energized individuals. Then, we did a sharing exercise with the leadership team, a buy-in process of sorts. I had to give them context around the goals, priorities for the team, and the sequence of one goal over another. They were interested in the framework, teams that were devised from the objectives, and the exact outcomes that we set for ourselves. As a result, we wrote a company-wide memo-style document so people would have an external narrative of what it was we were doing, how it contributed to the platform, and what we wanted to achieve by the following year’s end.

Lessons learned

  • "OKRs are a great goal setting framework because often times there is a lack of clarity on whether a team is hitting a goal or not. Yet, with OKRs you are forced to sign yourselves up for a clear objective that will result in a precise measurable outcome. This leads to fantastic accountability and clarity from the team on what is to be done and what they have to hit."
  • "There should be a discussion around whether to set conservative or ambitious goals. I’m always in favor of going for it and setting ambitious goals but this will depend on the state of your team. In this situation, my team’s morale was good and we had a centered direction, therefore striving for more helped push people beyond what they were capable of and allowed them to achieve that long-reaching goal."
  • "Due to the fact that we spent dedicated time with the team to come up with these goals and because we generated specific outcomes, the team felt invested and connected to the essence of the goals. It gave them the opportunity to ask questions and challenge the objectives while also paving the way for easy buy-in from individuals."
  • "The OKRs that we established were relatable and easy to understand. So much so that when someone new came into our work stream, or when somebody asked a peer a question, the conversation would ultimately return back to the objectives and key results. Individuals were able to see for themselves the larger picture, why certain goals were important, and the direction that we were headed. The OKRs acted as a self-alignment tool."
  • "Three is a good number to stick to when establishing annual OKRs. Any more and there’s suddenly too many goals and none of them are super important. Too little and people will hyper-focus on them. Preferably three OKRs, three initiatives. They are easy to remember and you can incorporate the well-roundedness of what your organization wants to achieve."
  • "Another by-product of the annual OKRs was that we were able to get a very clear handle on what success looked like. It gave the team extreme clarity on priorities. It also empowered everyone on the team to ask questions and determine whether a task was contributing to our goals. Instead of picking up random work from here and there, individuals were really focused on the objectives and what we wanted to achieve by the end of the year."

Be notified about next articles from Paritosh Aggarwal

Paritosh Aggarwal

Engineering Manager at Airbnb

Engineering LeadershipLeadership DevelopmentCommunicationOrganizational StrategyEngineering ManagementPerformance MetricsLeadership TrainingLeadership & StrategyTeam & Project ManagementDirector of Engineering

Connect and Learn with the Best Eng Leaders

We will send you a weekly newsletter with new mentors, circles, peer groups, content, webinars,bounties and free events.


HomeCircles1-on-1 MentorshipBountiesBecome a mentor

© 2024 Plato. All rights reserved

LoginSign up