OKRs Examples

/

IT

OKRs for IT Department

Why use OKRs?

IT departments are mostly inward facing. That is, they focus on optimizing internal processes to ensure that employees are able to do their best work while keep customer data safe and secure.

OKRs can help set a clear direction every quarter to focus on specific parts of the organization, or to improve certain processes.

Key questions:

Are we happy with general safety and security protocols?

Are requests handled in a timely manner?

Are employees generally happy with their work environment?

Do we need to review the IT budget?

Examples of Information Technology OKRs

You'll find below some OKRs examples to take inspiration from. Your OKRs should move from quarter to quarter and map to your company's reality – use our examples as a starting point, and adapt to what's happening in your business.

OKRs to increase security awareness

Objective

Make security part of our culture

Key result

100% of employees have gone through security training

Key result

2FA is used on all 3rd party services used by employees

Key result

Roll out fleet management pilot to 30% of the company

More OKR templates →

OKRs to improve the Disaster Recovery process

Objective

Have a world class DR process

Key result

Reduce recovery period from 24h to 12h

Key result

Reduce recovery point objective from 12 business hours to 4 business hours

Key result

Increase the number of DR tests from 1 to 3 per quarter

More OKR templates →

OKRs to improve incident management

Objective

Build an amazing incident management process

Key result

Increase the size of the incident response team from 2 to 6 people

Key result

Reduce the MTTR from 3h to 60 minutes

Key result

Reduce the number of regressions by 60%

More OKR templates →

OKRs to accelerate dev speed

Objective

Support developers by improving dev speed

Key result

Reduce average build time from 20mins to 2mins

Key result

90% of products have a standardized Continous Delivery pipeline

Key result

Reduce release cycle from 12 days to 3 days

More OKR templates →

Tracking your OKRs

Knowing how to write good OKRs is critical, but without good tracking in place, the OKRs will fade away and focus will be lost.

It's not just us saying that:

The easier it is for a team to have weekly discussions around the OKRs, the better they'll execute.

But today, many teams still keep their OKRs in spreadsheets. It's a great way to learn (we encourage them for the first cycle), but they quickly get in the way as you start to scale your OKRs process.

Instead, we recommend using Tability to facilitate the check-ins process and reduce the time spent building reports.

Tability will act as your accountability buddy for your OKRs by sending you reminders when updates are due. Then you'll be able to update progress rapidly and get reports and dashboards out of the box.

What other IT metrics can you use?

If you’re looking for some inspiration, here are some example of metrics that can be relevant for your Key Results.

Apdex

Apdex is an open standard for measuring performance of software applications.

Availability

Percentage of time when your service was running.

MTBF

Mean Time between System Failures

MTTR

Mean Time to Resolution

Asset maintenance cost

How much do you need to spend to maintain company assets.

Infrastructure expense per employee

How much do you spend on infrastructure per employee?

Training Expenses per Employee

How much is spent on personal development and training per Employee.

Stop wasting your OKRs. Focus on the right work and accomplish your goals.

Try Tability for free
Share