/templatesStart free
Browse all functions
Engineering OKR example

Make on-call sustainable

Reduce after-hours pages without missing real issues.

Suggested timeframe: Set with your team1 objective · 3 key results
YOUR STARTING POINTEngineering OKRs
OBJECTIVE

Reduce after-hours pages without missing real issues

  1. KR 1

    Cut after-hours pages from 30 to 8 per week

  2. KR 2

    Reduce non-actionable alerts from 60% to 15% of all alerts

  3. KR 3

    Raise on-call satisfaction from 4 to 7 out of 10

Example targets. Adapt to your baseline before you start.
USE THIS WHEN

On-call is burning people out. Audit alerts before setting targets.

KPIs to watch alongside this OKR

Keep these measures in view as you review progress.

  • After-hours pages
  • Actionable alert rate
  • On-call satisfaction
Explore related KPIs

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: Make on-call sustainable
objectives:
  - title: Reduce after-hours pages without missing real issues
    outcomes:
      - title: Cut after-hours pages from 30 to 8 per week
        initiatives: []
      - title: Reduce non-actionable alerts from 60% to 15% of all alerts
        initiatives: []
      - title: Raise on-call satisfaction from 4 to 7 out of 10
        initiatives: []
KEEP EXPLORING

More examples to explore.

Explore the collection
Team

Make developers productive from week one

Shorten the time it takes new engineers to contribute.

Objective

Shorten time to first meaningful contribution for new engineers

  1. Reduce time to first merged pull request from 10 days to 3 days
  2. Get local environment setup under 1 hour, down from 1 day
  3. Raise new-hire onboarding satisfaction from 6.5 to 8.5 out of 10
View template FROM PLAN TO PROGRESS

Make this plan yours.

Copy the template below, then open Tability. In your plan, choose Import goals from CSV or text and paste it into Import from text.

Create an account

Delivery

Ship faster without breaking things

Increase delivery speed while keeping failures low.

Objective

Increase delivery speed while keeping change failure low

  1. Increase deploys to production from 2 per week to daily
  2. Reduce lead time for changes from 8 days to 2 days
  3. Keep change failure rate under 10%, down from 18%
View template FROM PLAN TO PROGRESS

Make this plan yours.

Copy the template below, then open Tability. In your plan, choose Import goals from CSV or text and paste it into Import from text.

Create an account

Reliability

Cut production incidents

Make the product something customers can rely on.

Objective

Make our product something customers can rely on

  1. Reduce customer-facing incidents from 12 to 5 per quarter
  2. Cut mean time to recovery from 3 hours to 45 minutes
  3. Complete post-incident actions for 100% of major incidents within 2 weeks, up from 50%
View template FROM PLAN TO PROGRESS

Make this plan yours.

Copy the template below, then open Tability. In your plan, choose Import goals from CSV or text and paste it into Import from text.

Create an account

FROM PLAN TO PROGRESS

Make this plan yours.

Copy the template below, then open Tability. In your plan, choose Import goals from CSV or text and paste it into Import from text.

Create an account