OKRs are quickly gaining popularity as a goal-setting framework. But, it's not always easy to know how to write your goals, especially if it's your first time using OKRs.
That's why we have created a list of OKRs examples for Engineers to help. You can use any of the templates below as a starting point to write your own goals.
Examples of OKRs for Engineers
You'll find Objectives and Key Results for Engineers, but our examples may also include the tasks that can help you get there.
You'll find 7 OKRs examples for Engineers below, and some extra tips to write better quarterly plans at the end.
- Build a world-class infrastructure
- Increase Apdex above 0.95
- Cache requests wherever possible
- Identify and resolve to 5 application bottlenecks
- Reduce build time to be under 5 minutes
- Audit test suite to reduce duplicates
- Switch to a more performing build infrastructure
- Our stress tests show that we can support 10,000 concurrent users
- Tackle technical debt generated by feature rush
- Migrate 80% of projects to new UI library to reduce UI debt
- Reduce percentage of issues tagged as debt by 30%
- Reduce debt-related contact rate by 50%
- Accelerate development through automation
- 100% of repos have a Continuous Delivery pipeline
- Use Github Actions/Bitbucket Pipelines to automate deployments on every commit
- Create automated deployment scripts for all repos
- Increase code coverage from 30% to 60%
- Reduce cycle time from 8 days to 8h
- Reduce build time from 20min to 5min
- Audit tests to find areas of improvements
- Split tests to run in parallel when possible
- Significantly increase the speed of our development cycle
- Improve developer NPS from 20 to 60
- Reduce build times from 25 to under 5 mins
- Reduce cycle time from 28 days to 6 days
- Implement CD pipeline for the staging environment
- Automate all deployment steps
- Achieve amazing performance with a world-class infrastructure
- Increase Apdex from 0.7 to 0.98
- Add a CDN in front of resources
- Implement caching wherever possible
- Minify scripts and CSS
- Improve crash free sessions from 75% to 95%
- Reduce core pages load time to be under 3s
- Reduce the number of paged issues by 40%
- Identify and fix top 10 recurring issues
- Demonstrate incredible standards in code quality
- 100% of pull requests are reviewed by 2 developers
- 75% of the developers have gone through QA training
- 100% of repositories are using code linting and static code analysis
- Reduce the percentage of QA-related broken builds by 60%
- Significantly improve the user experience through better performance
- Decrease the number of production exceptions by 45%
- Accelerate customer instance cold start time from 2min to 10s
- Reduce API response time from 900ms to 450ms
- Improve NPS from 15 to 35
Not seeing what you need?
You can get a free custom-made template in 24h (no sign-up required).
How to track your OKRs?
It's important to establish a cadence of check-ins for your Engineers OKRs.
OKRs without regular progress updates are just KPIs. You'll need to update progress on your OKRs every week to get the full benefits from the framework.
We recommend using a spreadsheet for your first OKRs cycle. You'll need to get familiar with the scoring and tracking first. Then, you can scale your OKRs process by using a proper OKRs-tracking tool for it.
Here are a list of resources to help you adopt the Objectives and Key Results framework.