3 customisable OKR examples for Server Infrastructure

What are Server Infrastructure OKRs?

The Objective and Key Results (OKR) framework is a simple goal-setting methodology that was introduced at Intel by Andy Grove in the 70s. It became popular after John Doerr introduced it to Google in the 90s, and it's now used by teams of all sizes to set and track ambitious goals at scale.

Writing good OKRs can be hard, especially if it's your first time doing it. You'll need to center the focus of your plans around outcomes instead of projects.

We understand that setting OKRs can be challenging, so we have prepared a set of examples tailored for Server Infrastructure. Take a peek at the templates below to find inspiration and kickstart your goal-setting process.

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

Building your own Server Infrastructure OKRs with AI

While we have some examples available, it's likely that you'll have specific scenarios that aren't covered here. You can use our free AI generator below or our more complete goal-setting system to generate your own OKRs.

Feel free to explore our tools:

Our customisable Server Infrastructure OKRs examples

You'll find below a list of Objectives and Key Results templates for Server Infrastructure. We also included strategic projects for each template to make it easier to understand the difference between key results and projects.

Hope you'll find this helpful!

1. OKR to consolidate and streamline server infrastructure

  • ObjectiveConsolidate and streamline server infrastructure
  • Key ResultCreate comprehensive upgrade plan for remaining servers
  • TaskAnalyze necessary improvements for each server
  • TaskIdentify all servers that require an upgrade
  • TaskSketch a detailed upgrade timeline
  • Key ResultImplement updated server technology in 40% of systems
  • TaskIdentify the systems suitable for updated server technology
  • TaskCommence 40% system upgrade with updated server technology
  • TaskPrepare servers for technology upgrades in chosen systems
  • Key ResultReduce active servers by 15% without impacting performance
  • TaskExecute server consolidation without affecting user experience
  • TaskIdentify least-occupied servers and potential consolidation opportunities
  • TaskMonitor server performance regularly post-consolidation

2. OKR to ensure up-to-date server infrastructure

  • ObjectiveEnsure up-to-date server infrastructure
  • Key ResultAchieve 100% completion of server vulnerability patches
  • TaskDevelop or source needed patches
  • TaskIdentify all existing server vulnerabilities
  • TaskImplement patches on all servers
  • Key ResultIncrease automated update success rate to 98%
  • TaskMonitor and analyze failed updates for improvements
  • TaskEnhance testing procedures for all automated updates
  • TaskImprove error handling mechanisms in the automation code
  • Key ResultDecrease server down-time during updates by 30%
  • TaskUtilize rolling updates to minimize interruption
  • TaskImplement automated backup and recovery systems
  • TaskEnhance predictive maintenance capabilities

3. OKR to streamline and automate IT infrastructure processes

  • ObjectiveStreamline and automate IT infrastructure processes
  • Key ResultImplement automation in 70% of server management tasks to enhance efficiency
  • TaskTrain the team on implementing automation processes
  • TaskIdentify the predominant server management tasks for automation
  • TaskResearch and select suitable automation tools
  • Key ResultDeploy desktop automation to reduce manual tasks in IT support by 50%
  • TaskPurchase and install necessary automation software
  • TaskIdentify repetitive, manual tasks in IT support for automation
  • TaskTrain IT support staff in automation usage
  • Key ResultDevelop an automated solution to resolve 60% of common network issues
  • TaskTest and implement the automation solution
  • TaskIdentify common network issues and their frequency
  • TaskDesign a prototype for automated issue resolution

Best practices for managing your Server Infrastructure OKRs

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.

Tability Insights DashboardTability's audit dashboard will highlight opportunities to improve OKRs

Tip #2: Commit to the weekly 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.

Tability Insights DashboardTability's check-ins will save you hours and increase transparency

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.

Best way to track your Server Infrastructure OKRs

The rules of OKRs are simple. Quarterly OKRs should be tracked weekly, and yearly OKRs should be tracked monthly. Reviewing progress periodically has several advantages:

  • It brings the goals back to the top of the mind
  • It will highlight poorly set OKRs
  • It will surface execution risks
  • It improves transparency and accountability

Spreadsheets are enough to get started. Then, once you need to scale you can use a proper OKR platform to make things easier.

A strategy map in TabilityTability's Strategy Map makes it easy to see all your org's OKRs

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 Server Infrastructure OKR templates

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

OKRs resources

Here are a list of resources to help you adopt the Objectives and Key Results framework.

Create more examples in our app

You can use Tability to create OKRs with AI – and keep yourself accountable 👀

Tability is a unique goal-tracking platform built to save hours at work and help teams stay on top of their goals.

Signup1 Create your workspace
Signup2 Build plans in seconds with AI
Signup3Track your progress
Quick nav