OKR Best Practices for Technology Teams

I recently sat down with some of NYC’s leading CTOs and heads of engineering to discuss OKR and KPI best practices. The truth is, despite the fact that 2018 is underway, many tech teams are still scrambling to finish 2018 annual planning.

It’s ok. Keep Calm.

I’m here to tell you — it’s ok. Keep Calm.

Whether you use OKRs, KPIs, Rocks, or any other annual and quarterly planning process, the key to success is to find a process that is flexible and is embraced by your team.

While there’s no one-size-fits-all solution, these OKR and annual planning best practices should hopefully get your team over the finish line:

Set a 3 year goal first

With the average tenure of today’s tech employee at 2 years, it’s important to keep in mind that a 20 or 10 year goal might seem to distant and unmotivating. Instead, anchor your team with a strong three year goal. Three years is a good amount of time for most tech teams. It’s long enough that it feels strategic and short enough that it’s motivating.Pro Tip: The 3 year goal should be measurable.

Get buy-in from the team early and often

People, in general, hate being told what to do. Ensure your team is on board with your annual plan by getting buy-in from them early and often. Enable employees to poke holes in the plan and suggest improvements to it. Give employees permission to be vocal about areas they want to be involved in.

Set expectations on what to do if you need to pivot mid-year

Annual planning doesn’t have to be anti-Agile. If done right, the annual plan can be a strong complement to a high functioning Agile team. Use Agile best practices to guide your annual planning session by setting a small handful of measurable initiatives, and account for slack time. Hold regular retrospectives, and create a process for pivoting or iterating on the plan that mirrors how you handle a new feature or epic or sprint planning.

Make it personal

Assign 1 person to be accountable for each OKR, each Rock, each KPI. Know who the product owner is for each initiative. Be crystal clear on the definition of “Done. Done.” Put the accountable person’s image next to the OKR. Whether you have an avatar, someone’s headshot, or a physical sign-off sheet, make it visible to the entire company who owns each initiative. For larger organizations, consider implementing RACI, or some other type of responsibility matrix, to create a shared understanding of the type of involvement various team members have in each initiative.

At Casper, each OKR owner presents their results to the entire team, regardless of how much of the goal they achieved.

Plan out your estimated capacity at the start of each quarter

Don’t go crazy with this, just figure out the ballpark capacity. How many person weeks do you expect to have, account for planned new hires, any anticipated turnover, holidays and vacations? With the ballpark idea of capacity, you can have a better chance of setting achievable velocity and outputs.

Don’t have 1 metric that everyone is trying to hit

Instead, have a small handful of 3–5 metrics, each with an owner. Ideally, product and engineering teams have adjacent and aligned goals, but not the same exact goal.

Growth and efficiency at the same time is really hard, pick one

Innovation is inefficient. Growth is inefficient. When you are doubling in size, be realistic about the temporary hit that velocity per employee is going to take. New employees need ramp up time and time to integrate with the team. So, when picking your OKRs, be realistic about the tradeoffs you are making when prioritizing either growth or efficiency.

Use a tool to track progress against OKRs

Jira, Trello, Google Docs, Metronome, Clubhouse. Pick one tool, use it. It matters less which tool you choose. It matters more that you use it consistently. Just like you track progress towards epics and stories, track progress towards OKRs. Set a cadence for tracking progress and stick with it. You might choose to track OKR progress as part of each sprint, or you might choose to hold distinct meetings to review OKR progress.

What best practices have you seen? What mistakes have you made? Add your OKR best practices in the comments below.

For a Fortune 100 media firm, predicting viewership was crucial to revenue — so they turned to Stride to rapidly prototype a solution using Agile programming. Read the full success story.

Senior, Lead, or Principal developer in NYC? Stride is hiring! Want to level up your tech team? See how we do it! www.stridenyc.com

Originally posted on the Stride Blog. Author: Debbie Madden

OKR Best Practices for Technology Teams was originally published in Hacker Noon on Medium, where people are continuing the conversation by highlighting and responding to this story.