OKR example: Implement disaster recovery plan with RTO under one hour
A starting point for clearer priorities and measurable progress. Make the targets your own.
Suggested timeframe: Set with your team1 objective · 4 key results
YOUR STARTING POINTTeam OKRs
OBJECTIVE
Increase disaster recovery efficiency
KR 1
Provide training on disaster recovery procedures to all relevant staff
KR 2
Conduct disaster recovery test bi-monthly
KR 3
Reduce RTO to under one hour
KR 4
Ensure all critical systems are covered in the recovery plan
Ideas to get you moving
Evaluate effectiveness of training and adjust as necessary
Identify key stakeholders for disaster recovery training
Develop customized training plan and materials
Schedule and conduct training sessions
Conduct test scenario walkthrough with all relevant stakeholders
Prepare disaster recovery plan documentation
Analyze results, identify gaps, and update disaster recovery plan accordingly
Execute disaster recovery test to validate plan and processes
Improve network bandwidth and reliability
Implement automated backup system
Test Disaster Recovery Plan regularly
Increase server redundancy
Identify all critical systems
Develop recovery strategies for critical systems
Determine the impact of system downtime
Test the recovery plan for critical systems
Example targets. Adapt to your baseline before you start.
About this template
A disaster recovery plan that has never been tested is a guess. This template is for IT teams that need to know how long a real recovery takes.
The headline result is an RTO under one hour. Supporting it, all critical systems are covered in the recovery plan, recovery tests run bi-monthly, and all relevant staff are trained on the procedures.
Record your current RTO from an actual test before setting anything else. "Bi-monthly" can mean twice a month or every two months, so state which. Every two months gives you one or two tests in a quarter, which is thin evidence for the hour.
Make it work for your team
01
Set your baseline. Check where you are today, then choose targets that stretch your team.
02
Agree on ownership. Give each key result a clear owner and a source of data.
03
Check in every week. Review the numbers, share confidence, and decide what needs attention.
Get this template as YAML
A machine-readable version of this example for a script or AI assistant.
---
title: Implement disaster recovery plan with RTO under one hour
objectives:
- title: Increase disaster recovery efficiency
outcomes:
- title: Provide training on disaster recovery procedures to all relevant staff
from: 0.0
to: 100.0
score_format: _number_%
initiatives:
- title: Evaluate effectiveness of training and adjust as necessary
- title: Identify key stakeholders for disaster recovery training
- title: Develop customized training plan and materials
- title: Schedule and conduct training sessions
- title: Conduct disaster recovery test bi-monthly
from: 0.0
to: 100.0
score_format: _number_%
initiatives:
- title: Conduct test scenario walkthrough with all relevant stakeholders
- title: Prepare disaster recovery plan documentation
- title: Analyze results, identify gaps, and update disaster recovery plan accordingly
- title: Execute disaster recovery test to validate plan and processes
- title: Reduce RTO to under one hour
from: 0.0
to: 100.0
score_format: _number_%
initiatives:
- title: Improve network bandwidth and reliability
- title: Implement automated backup system
- title: Test Disaster Recovery Plan regularly
- title: Increase server redundancy
- title: Ensure all critical systems are covered in the recovery plan
from: 0.0
to: 100.0
score_format: _number_%
initiatives:
- title: Identify all critical systems
- title: Develop recovery strategies for critical systems
- title: Determine the impact of system downtime
- title: Test the recovery plan for critical systems