Get Tability: OKRs that don't suck | Learn more →

5 OKR examples for Running

Turn your spreadsheets into OKR dashboards with Tability

Tability is a cheatcode for goal-driven teams. Set perfect OKRs with AI, stay focused on the work that matters.

What are Running 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.

Crafting effective OKRs can be challenging, particularly for beginners. Emphasizing outcomes rather than projects should be the core of your planning.

We've tailored a list of OKRs examples for Running to help you. You can look at any of the templates below to get some inspiration for your own goals.

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

The best tools for writing perfect Running OKRs

Here are 2 tools that can help you draft your OKRs in no time.

Tability AI: to generate OKRs based on a prompt

Tability AI allows you to describe your goals in a prompt, and generate a fully editable OKR template in seconds.

Watch the video below to see it in action 👇

Tability Feedback: to improve existing OKRs

You can use Tability's AI feedback to improve your OKRs if you already have existing goals.

AI feedback for OKRs in Tability

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.

Running OKRs examples

You will find in the next section many different Running Objectives and Key Results. We've included strategic initiatives in our templates to give you a better idea of the different between the key results (how we measure progress), and the initiatives (what we do to achieve the results).

Hope you'll find this helpful!

OKRs to consistently rank in the top half of running events

  • ObjectiveConsistently rank in the top half of running events
  • KRParticipate in 3 local running events to gain race experience
  • TaskStart a regular training schedule
  • TaskRegister for the chosen 3 running events
  • TaskResearch local running events in your area
  • KRIncrease weekly mileage by 10% to improve overall endurance
  • TaskCalculate current weekly mileage for accurate increment
  • TaskConsistently monitor progress and endurance level
  • TaskGradually increase mileage by 10% each week
  • KRFinish five 10k runs in under 50 minutes for enhanced speed
  • TaskSchedule weekly training to progressively increase running speed
  • TaskIncorporate high-intensity interval training in workouts
  • TaskMonitor time on each run and adjust pace

OKRs to become better at running

  • ObjectiveImprove Long Distance Running Performance
  • KRIncrease endurance by running 4 times per week
  • KRIncrease speed by completing interval training sessions twice per week
  • KRImprove 5K race time by 20%

OKRs to keep a long-running project on track

  • ObjectiveThe ACH Payment project is on track for next quarter
  • KRWe have achieve our 4 main development milestones
  • TaskMilestone 1: UX Design completed
  • TaskMilestone 4: We have enrolled 10 beta customers on ACH
  • TaskMilestone 2: Backend API is functional and tested
  • TaskMilestone 3: ACH payment is wired to the UI (internal)
  • KRWe have completed 25 transactions on the internal beta
  • KRWe have completed 20 UX testing sessions

OKRs to improve team effectiveness in running operations

  • ObjectiveImprove team effectiveness in running operations
  • KREnhance team efficiency by reducing average response time to customer inquiries by 25%
  • TaskStreamline internal processes and workflows to minimize response time and avoid unnecessary delays
  • TaskImplement automated email templates for quick and standardized responses to customer inquiries
  • TaskProvide regular training sessions on effective communication and problem-solving techniques
  • TaskImplement a ticketing system to track and prioritize customer inquiries for faster resolution
  • KRIncrease team productivity by 15% through improved task management and delegation
  • TaskDefine clear goals and deadlines for each team member to improve task prioritization
  • TaskConduct regular feedback sessions to address challenges and provide support in task management
  • TaskProvide training on effective delegation strategies to enhance productivity within the team
  • TaskImplement a centralized task management system for better tracking and collaboration
  • KRImprove team collaboration by achieving a 30% increase in cross-functional communication and information sharing
  • TaskProvide training sessions on effective communication and active listening skills for team members
  • TaskEncourage knowledge sharing and collaboration through a central online platform or shared documents
  • TaskFacilitate cross-functional team building activities to strengthen relationships and promote communication
  • TaskImplement regular team meetings to discuss projects, share updates, and address challenges
  • KRReduce operational errors by 20% through enhanced documentation and quality control

OKRs to be on track for a long-running project

  • ObjectiveBe on track to deliver <project> next quarter
  • KR100% of the core features have been delivered
  • TaskShip <feature 2>
  • TaskShip <feature 1>
  • TaskIdentify all core features
  • KRRun 20 UX tests session on <project>
  • TaskAnalyze feedback and identify opportunities
  • TaskCreate the UX test script
  • KR50 people are actively using the beta every week

Running 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.

Save hours with automated OKR dashboards

AI feedback for OKRs in Tability

Your quarterly OKRs should be tracked weekly if you want 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, you can move to Tability to save time with automated OKR dashboards, data connectors, and actionable insights.

How to get Tability dashboards:

That's it! Tability will instantly get access to 10+ dashboards to monitor progress, visualise trends, and identify risks early.

More Running OKR templates

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

Table of contents