A starting point for clearer priorities and measurable progress. Make the targets your own.
Suggested timeframe: Set with your team1 objective · 3 key results
YOUR STARTING POINTTeam OKRs
OBJECTIVE
Successfully sunset Rapid7 platform
KR 1
Identify and document all dependencies on the Rapid7 platform by the end of Q1
KR 2
Develop and test a migration strategy for 70% of identified dependencies
KR 3
Effectively communicate changes to all stakeholders, achieving an 80% understanding rate
Ideas to get you moving
Catalog all applications using Rapid7 platform
Document configuration settings and usages
List associated modules and external connections
Develop a migration strategy for identified dependencies
Identify and list all software and system dependencies
Execute, monitor, and test the migration strategy
Conduct surveys to gauge comprehension level
Clearly outline changes in an easily understandable format
Arrange communication sessions for detailed explanation
Example targets. Adapt to your baseline before you start.
About this template
The primary aim of the OKR is the successful sunset of the Rapid7 platform by the end of the year. Initially, all dependencies on the Rapid7 platform are to be identified and documented by the end of the first quarter. This will include cataloguing applications using the platform, documenting configuration settings and usages, and listing associated modules and external connections.
The second outcome aims at developing and testing a migration strategy for 70% of the identified dependencies. This entails formulating a migration plan and identifying and listing all software and system dependencies. Execution, monitoring, and testing of the migration strategy form the initiatives for this outcome.
The third objective involves an active and effective communication of the changes to all stakeholders, achieving an 80% understanding rate. Comprehension level amongst stakeholders is to be gauged using surveys. The changes are to be outlined clearly and in an easily comprehensible format. Detailed explanation sessions will be arranged for a better understanding of the changes.
In order to have a highly successful sunset of Rapid7, the OKR proposes a phased approach starting from identifying all dependencies, developing an effective migration and communication strategy, to ensuring a vast understanding rate among stakeholders.
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: Successfully sunset Rapid7 platform
objectives:
- title: Successfully sunset Rapid7 platform
outcomes:
- title: Identify and document all dependencies on the Rapid7 platform by the end
of Q1
from: 0.0
to: 100.0
score_format: _number_%
initiatives:
- title: Catalog all applications using Rapid7 platform
- title: Document configuration settings and usages
- title: List associated modules and external connections
- title: Develop and test a migration strategy for 70% of identified dependencies
from: 0.0
to: 100.0
score_format: _number_%
initiatives:
- title: Develop a migration strategy for identified dependencies
- title: Identify and list all software and system dependencies
- title: Execute, monitor, and test the migration strategy
- title: Effectively communicate changes to all stakeholders, achieving an 80% understanding
rate
from: 0.0
to: 100.0
score_format: _number_%
initiatives:
- title: Conduct surveys to gauge comprehension level
- title: Clearly outline changes in an easily understandable format
- title: Arrange communication sessions for detailed explanation
Team OKR example
Suggested timeframe: Set with your team
1 objective · 3 key results
Example targets. Adapt to your baseline before you start.