Discover Tability: the AI platform that turns OKRs into resultsLearn more →

2 OKR examples for Data Driven Decisions

What are Data Driven Decisions OKRs?

The OKR acronym stands for Objectives and Key Results. It's a goal-setting framework that was introduced at Intel by Andy Grove in the 70s, and it became popular after John Doerr introduced it to Google in the 90s. OKRs helps teams has a shared language to set ambitious goals and track progress towards them.

Formulating strong OKRs can be a complex endeavor, particularly for first-timers. Prioritizing outcomes over projects is crucial when developing your plans.

To aid you in setting your goals, we have compiled a collection of OKR examples customized for Data Driven Decisions. Take a look at the templates below for inspiration and guidance.

If you want to learn more about the framework, you can read our OKR guide online.

How to write your own Data Driven Decisions OKRs

Option 1. Turn ideas into OKRs with Tability AI

While we have some examples available, it's likely that you'll have specific scenarios that aren't covered here.

You can use Tability's AI generator to create tailored OKRs based on your specific context. Tability can turn your objective description into a fully editable OKR template -- including tips to help you refine your goals.

Tability will then use your prompt to generate a fully editable OKR template.

Watch the video below to see it in action 👇

Option 2. Optimise existing OKRs with Tability Feedback tool

If you already have existing goals, and you want to improve them. You can use Tability's AI feedback to help you.

AI feedback for OKRs in TabilityTability's Strategy Map makes it easy to see all your org's OKRs

Tability will scan your OKRs and offer different suggestions to improve them. This can range from a small rewrite of a statement to make it clearer to a complete rewrite of the entire OKR.

You can then decide to accept the suggestions or dismiss them if you don't agree.

Option 3. Use the free OKR generator

If you're just looking for some quick inspiration, you can also use our free OKR generator to get a template.

Unlike with Tability, you won't be able to iterate on the templates, but this is still a great way to get started.

Data Driven Decisions OKRs examples

We've added many examples of Data Driven Decisions Objectives and Key Results, but we did not stop there. Understanding the difference between OKRs and projects is important, so we also added examples of strategic initiatives that relate to the OKRs.

Hope you'll find this helpful!

OKRs to enhance Support Systems and Tools for data-driven decisions

  • ObjectiveEnhance Support Systems and Tools for data-driven decisions
  • KRDevelop and integrate an advanced analytics platform into the current system
  • TaskIdentify required features and capabilities for the analytics platform
  • TaskImplement and test the analytics platform integration
  • TaskDevise a suitable integration strategy for current system
  • KRAchieve 25% increase in data-driven decisions by the end of the next quarter
  • TaskImplement and enforce a data-first policy in decision-making processes
  • TaskEstablish weekly KPI tracking and reviews
  • TaskProvide training on data analysis to the decision-makers
  • KRTrain 80% of team members on data analysis with new tools
  • TaskAssess and monitor their tool proficiency post-training
  • TaskIdentify team members needing data analysis training
  • TaskSchedule and conduct training sessions for these members

OKRs to drive change for a better future based on data and evidence

  • ObjectiveDrive change for a better future based on data and evidence
  • KRSuccessfully influence 70% of stakeholders to support necessary change initiatives
  • TaskOrganize personalized meetings with these stakeholders to garner support
  • TaskIdentify key stakeholders and their main concerns about the change
  • TaskCreate a compelling case for the change using data points
  • KRPresent robust data-driven insights to key stakeholders with 100% completion
  • TaskDevelop a comprehensive presentation of findings
  • TaskSchedule and conduct presentation to stakeholders
  • TaskIdentify and analyze relevant data for key insights
  • KRAchieve a 30% progress in proposed changes based on received feedback and results
  • TaskImplement and document first 30% of prioritized changes
  • TaskPrioritize changes based on impact and feasibility
  • TaskReview feedback and results for proposed changes

Data Driven Decisions OKR best practices

Generally speaking, your objectives should be ambitious yet achievable, and your key results should be measurable and time-bound (using the SMART framework can be helpful). It is also recommended to list strategic initiatives under your key results, as it'll help you avoid the common mistake of listing projects in your KRs.

Here are a couple of best practices extracted from our OKR implementation guide 👇

Tip #1: Limit the number of key results

The #1 role of OKRs is to help you and your team focus on what really matters. Business-as-usual activities will still be happening, but you do not need to track your entire roadmap in the OKRs.

We recommend having 3-4 objectives, and 3-4 key results per objective. A platform like Tability can run audits on your data to help you identify the plans that have too many goals.

Tip #2: Commit to weekly OKR check-ins

Don't fall into the set-and-forget trap. It is important to adopt a weekly check-in process to get the full value of your OKRs and make your strategy agile – otherwise this is nothing more than a reporting exercise.

Being able to see trends for your key results will also keep yourself honest.

Tip #3: No more than 2 yellow statuses in a row

Yes, this is another tip for goal-tracking instead of goal-setting (but you'll get plenty of OKR examples above). But, once you have your goals defined, it will be your ability to keep the right sense of urgency that will make the difference.

As a rule of thumb, it's best to avoid having more than 2 yellow/at risk statuses in a row.

Make a call on the 3rd update. You should be either back on track, or off track. This sounds harsh but it's the best way to signal risks early enough to fix things.

How to track your Data Driven Decisions OKRs

Your quarterly OKRs should be tracked weekly in order to get all the benefits of the OKRs framework. Reviewing progress periodically has several advantages:

Most teams should start with a spreadsheet if they're using OKRs for the first time. Then, once you get comfortable you can graduate to a proper OKRs-tracking tool.

If you're not yet set on a tool, you can check out the 5 best OKR tracking templates guide to find the best way to monitor progress during the quarter.

More Data Driven Decisions OKR templates

We have more templates to help you draft your team goals and OKRs.

Table of contents